Closed myusrn closed 5 years ago
Hi, @myusrn. The prerequisites state that .NET Core 2.2 SDK is needed for this tool. Retry it with 2.2 instead of 3.0 preview and you should be good to go. Closing as this issue is resolved. Thanks!
Thanks for details. Is there a way to tell dotnet tool install -g mlnet
command to use the 2.2 sdk versus the vs19 installed 3.0.100-preview# sdk versus having to uninstall it?
Try dotnet tool update -g mlnet --framework netcoreapp2.2
Thanks for those details. Doing more testing the issue was not arising from the presence of the vs19 installed dotnet core 3.0.100-preview sdk. It was a result of the 401 accessed denied arising when the dotnet tool install/update . . .
command attempted to iterate through my set of defined nuget feeds and hit the one pointing at my azure devops nuget package feed where it appears there are no cached credentials in place. I used vs19 | tools | options | nuget pacakage manager | package sources UI to uncheck/disable that package feed and after that the dotnet tool install/update -g mlnet
command to succeed with dotnet core 3.0 sdk preview installed.
I execute the command "> dotnet tool update -g mlnet" and it produces the following output. If this is just expected to work as the page suggests then it would seem a dependency or command parameter, e.g. --version #.#.# , is missing from the instructions.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.