It seems that MDV is not packaged properly as dotnet tool
kant2002 opened this issue · 2 comments
kant2002 commented
I did try run
dotnet tool install -g --prerelease --add-source https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-tools/nuget/v3/index.json mdv
but receive
error NU1212: Invalid project-package combination for mdv 1.0.0-beta3.22306.2. DotnetToolReference project style can only contain references of t
he DotnetTool type
The tool package could not be restored.
Tool 'mdv' failed to install. This failure may have been caused by:
* You are attempting to install a preview release and did not use the --version option to specify the version.
* A package by this name was found, but it was not a .NET tool.
* The required NuGet feed cannot be accessed, perhaps because of an Internet connection problem.
* You mistyped the name of the tool.
For more reasons, including package naming enforcement, visit https://aka.ms/failure-installing-tool
which based on https://docs.microsoft.com/en-us/dotnet/core/tools/troubleshoot-usage-issues#package-isnt-a-net-tool indicates that Nuget package has invalid setup, and package MDV as regular Nuget package, and not tool package.
tmat commented
That's correct, mdv is currently not a tools package.
kant2002 commented
I apologize then. I somehow was under impression when read source code that this is should be the case. Especially because I see mdv
package on Nuget feed. Looks like I misinterpret things.