You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Improve error message on missing dll in dotnet runtime
General
Trying to run dotnet Some.NonExistent.dll with just the dotnet runtime produces a misleading error message telling us that we're missing the SDK instead of telling us that the file is missing. Could the runtime display the same error message as the SDK?
The situation was that we had a tiny spelling error in the script running the app in a docker container, and it wasn't at all apparent that we had misspelled the dll name, spent a fair amount of time trying to figure out what was wrong.
Steps to reproduce
Example using the docker dotnet runtime image:
PS C:\> docker pull mcr.microsoft.com/dotnet/core/runtime:3.0
PS C:\> docker run -it --entrypoint /bin/bash mcr.microsoft.com/dotnet/core/runtime:3.0
root@6f87t213c05f:/# dotnet Some.NonExistent.dll
It was not possible to find any installed .NET Core SDKs
Did you mean to run .NET Core SDK commands? Install a .NET Core SDK from:
https://aka.ms/dotnet-download
Expected behavior
I would be great that the runtime had the same behavior as the SDK. Running this on my local machine I get an error message I can understand.
PS C:\> dotnet Some.NonExistent.dll
Could not execute because the specified command or file was not found.
Possible reasons for this include:
* You misspelled a built-in dotnet command.
* You intended to execute a .NET Core program, but dotnet-Some.NonExistent.dll does not exist.
* You intended to run a global tool, but a dotnet-prefixed executable with this name could not be found on the PATH.
The text was updated successfully, but these errors were encountered:
Improve error message on missing dll in dotnet runtime
General
Trying to run
dotnet Some.NonExistent.dll
with just the dotnet runtime produces a misleading error message telling us that we're missing the SDK instead of telling us that the file is missing. Could the runtime display the same error message as the SDK?The situation was that we had a tiny spelling error in the script running the app in a docker container, and it wasn't at all apparent that we had misspelled the dll name, spent a fair amount of time trying to figure out what was wrong.
Steps to reproduce
Example using the docker dotnet runtime image:
Expected behavior
I would be great that the runtime had the same behavior as the SDK. Running this on my local machine I get an error message I can understand.
The text was updated successfully, but these errors were encountered: