Open ineternet opened 10 months ago
@arkalyanms @AArnott @lifengl Which do you think should take preference here? I agree with the user that the explicit setting should take preference, in which case this would need to be changed in the CDK .NET Selection code.
Personally, I don't have this issue anymore because I was able to change the location of the preferred dotnet install in PATH. But that assumes an environment where you can do this just to make one workspace/project work. Might not be ideal if you are working on multiple things at once that each require a different dotnet install.
+1 on the explicit setting taking precendence. @nagilson would you work with @lifengl to drive closure?
I would be happy to do so 😄
Describe the Issue
Like described in #314 or #138 I put the
existingDotnetPath
setting in my settings.json, but the tool detects a dotnet somewhere else, and uses that. This is an issue for me because this other dotnet doesn't have the correct SDKs installed.Steps To Reproduce
settings.json
:Expected Behavior
Either the option
existingDotnetPath
should take precedence, or there needs to be a way to make it stop autodetecting preinstalled SDKs and force a download.Environment Information
VS Code: 1.84.2 (user setup) C# extension: v2.12.19 C# Dev Kit extension: v1.0.14 .NET Install Tool: v2.0.0