Open AraHaan opened 2 years ago
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.
Can you clarify? MSBuild SDKs from NuGet shouldn't be installed to the dotnet install directory - that is unsupported. The NuGet MSBuild SDK resolver should download them from NuGet feeds automatically without the user having to mutate their environment.
Can you clarify? MSBuild SDKs from NuGet shouldn't be installed to the dotnet install directory - that is unsupported. The NuGet MSBuild SDK resolver should download them from NuGet feeds automatically without the user having to mutate their environment.
The msbuild sdk side is directly installed in the nuget packages cache folder, but the shared framework ref pack is then stored in the install directory.
Describe the bug
Let's say for example you installed a workload that installs it's own msbuild Sdks into $DOTNET_ROOT/packs along with it's reference assembly packs. Now when you load a project in Visual Studio that directly imports said Sdk the load of the project files will fail because it will look for them in $DOTNET_ROOT/sdk/[version]/Sdks and fail.
To Reproduce
To reproduce:
dotnet tool install --global Elskom.Net.Check
and runelskom-check
(run as admin first though so it can add files into $DOTNET_ROOT).<Project Sdk="Microsoft.NET.Sdk">
node to<Project Sdk="Elskom.Sdk">
and save the file.Exceptions (if any)
The exception is that it will not be able to find the Sdk that my cli tool does actually install.
Further technical details
dotnet --info
Visual Studio 2022 17.4.0 Preview 1.