New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dotnet tool restore
cannot find the local manifest file
#33921
Comments
@JL03-Yue can you take a look at this? It might be related to your recent fix. |
dotnet tool restore
is not finding the local manifest filedotnet tool restore
cannot find the local manifest file
Some more info: This only happens when the source code is placed in the root like To reproduce: subst x: c:\path\to\source
cd x:
dotnet tool restore |
In the latest version of dotnet, we made a change to not looking at the root for manifest file for security reasons for windows. This might affect the outcome of your command |
I was also affected by it. We use subst to workaround some tools that don't work on docker-mounted folders directly by works on subst drive for it and to make stable path written in pdb. With it, root of repository become root of drive - and it is very inconvenient that dotnet tool restore doesn't work for it. |
The breaking change document Tool manifests in root folder mentions that the original behaviour can be restored by setting the |
Thank you @KalleOlaviNiemitalo, the original behaviour can be restored by setting the DOTNET_TOOLS_ALLOW_MANIFEST_IN_ROOT environment variable. |
Describe the bug
After upgrading dotnet to 7.0.9,
dotnet tool restore
cannot find the manifest file in.config/dotnet-tools.json
It returns:
Running
dotnet new tool-manifest
will reset the manifest file and after adding the tools it still do not pick those tools up.Affected platforms
This only happens on Windows. MacOS seems to work. Have not tried linux.
To Reproduce
dotnet new tool-manifest
dotnet tool install Cake.Tool --version 3.1.0
will also fail with same error)dotnet tool restore
.config/dotnet-tools.json
Further technical details
dotnet --info
The text was updated successfully, but these errors were encountered: