search

coapp / coapp.powershell

ClrPlus Signing
52 stars 43 forks source link

Hide overlay packages in the package manager #34

Open yodantauber opened 11 years ago

yodantauber commented 11 years ago

I suppose you'd need to cooperate with the NuGet fellows for this one, but it would be really nice if the overlay packages you're never supposed to install anyway did not appear in the list of available packages in Visual Studio.

fearthecowboy commented 11 years ago

Actually, in practice this won't be much of a problem -- when we start uploading the packages to repositories, the (CoApp provided) publish-package cmdlet actually marks the overlay packages as unlisted so they don't show up in the dialog.

They will show up if you have them in a folder as a package source though. I don't know of any way to fix that.

yodantauber commented 11 years ago

Oh, well. I guess I'll have to live with that.

gordonwatts commented 11 years ago

This is very nice! Does publish-package work now? It would be nice if, in general, there was a "bit" that was set in the package description... (I understand why it isn't), as there are a lots of nuget servers out there (e.g. the teamcity one, etc.).

fearthecowboy commented 11 years ago

It should work right now. give it a try :D

NuGet servers should all support 'unlisting' (which removes the package from advertisement, but doesn't remove the package)

gordonwatts commented 11 years ago

I will soon: my packages aren't quite ready for being made public (they are currently too big, splitting them is the next project). I mentioned teamcity b.c. it has a nuget feed built in, and when I do my test builds, I use it. Of course, it has its own ingestion system, so I'll need to read up on that.

23W commented 9 years ago

I have uploaded my packages on NuGet with overlays. Now, they are in the general list. Is it enough to press unlist check that they were not visible but made available to users?