NuGet.org handling of tool packages

[nkolev92]

As part of the global tools work, NuGet side spec, we will introduce a new package type.

The name of this package type is to be determined, I will update when that's done.

The 2 requests are the following:

• NuGet.org should reject packages that include the global package tool and any other package type
• Packages with this package type should display a “dotnet install packageId packageVersion” tab only, rather than the standard tabs.

This will need to be live in the 15.7 timeline of Visual Studio, potentially earlier tbd.

//cc
@rrelyea
@NuGet/nuget-client
@joelverhagen
@anangaur
@KathleenDollard

[wli3]

What is the statues on this issue? A MVP asked about toady. A tool package will show up as, in nuget.org

dotnet add package my.tool --version aVersion

[wli3]

mock up and this is wrong

[nkolev92]

/cc
@skofman1 was this scheduled at some point?

[nkolev92]

It's a very small change server-side, I'll do some investigation within the next week or 2.

Does that work for you @wli3 ?

[maartenba]

Any docs on the small server change?

[joelverhagen]

Any docs on the small server change?

We will be using package type in the package .nuspec to toggle this behavior. Package types are currently persisted in our gallery DB. This is not a protocol change and only relates to gallery web UI behavior.

[maartenba]

Got it. Asked because there is an issue that also talks about exposing this (even thing there is a PR for it on search service), hence.

[wli3]

the correct one should be

dotnet install tool --global my.tool --version 1.0.0
cc @KathleenDollard

[nkolev92]

Verified fix on dev.
//cc @skofman1 @joelverhagen

[loic-sharma]

/cc @nkolev92 This is deployed to prod. I verified the dotnet watch tool: https://www.nuget.org/packages/dotnet-watch/2.1.0-preview1-final