Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

.NET Core Installer vs .NET Core Cli Installers is confusing

See original GitHub issue

I installed .NET Core Installer and wanted to confirm that I have the latest version and got:

PS C:\WINDOWS\system32> dotnet --version
Could not resolve SDK directory from [C:\Program Files\dotnet]

I did see that --help options in the new thing were limited but was not aware that I need a different installer to do my dev work. This is quite confusing since the tutorials say you should do dotnet build, dotnet run etc. but if you install just the Core Installer nothing of this works. The message and --help is very unhelpful either.

Issue Analytics

State:
Created 7 years ago
Reactions:7
Comments:14 (10 by maintainers)

Top GitHub Comments

4reactions

moozzykcommented, Mar 25, 2016

Yes, @anurse explained it too me. But users don’t have @anurse or you around - the message should make it possible to figure it out on my own. At the moment is is not helpful.

2reactions

akoeplingercommented, Mar 29, 2016

You could call it .NET Core Command Line Interface (CLI) similar to the SDK. I agree that Tools is more confusing even though there are different CLI meanings.