0

I am trying to make a completely portable .net core development environment. I have everything set up and portable except Visual Studio Code is looking for the dotnet cli in the default location on the c: drive. Can I change the path to the dotnet core sdk cli in Visual Studio Code and if so, where?

  • Does this help: https://github.com/dotnet/cli/issues/8530 – Arun Aug 14 '18 at 20:37
  • Unfortunately no. They are talking about the MSBuild process. I am just trying to get the dotnet new console command to execute without error. When I run the new command I get the following error: dotnet : The term 'dotnet' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At line:1 char:1 + dotnet new console – Jason Presley Aug 14 '18 at 20:45
  • This might help https://stackoverflow.com/a/42800519/8534630 – Arun Aug 14 '18 at 20:49
  • Does not look like what I am trying to do is possible. If I have to modify anything on the host OS then it is not truly portable. I was hoping for a setting in Visual Studio Code pointing to the CLI but everything I am seeing involves changing settings on the host. – Jason Presley Aug 14 '18 at 22:56
  • It is not VSCode, but the OmniSharp project that implements the C# support. Documentation seems to be sparse, so many times you need to dig the code base, https://github.com/OmniSharp/omnisharp-vscode or ask the developers. – Lex Li Aug 14 '18 at 23:59

0 Answers0