@stijn-peeters-external_8202 Thanks for letting us know; we do have plans to improve this in ProGet 2023, and make it much easier to use.

Thank you, in my case this is an internal Nuget package that is deployed directly to Proget. I unlisted a package version in Proget and I see the listed property is false via fiddler but it still shows up in a visual studio search. By the way, I just created a new topic for my issue here. https://forums.inedo.com/topic/3514/unlisted-package-version-still-shows-up-in-visual-studio

Thank you for the followup, that is good information. For future reference, the docs for switching from the built-in webserver to IIS can be found here: https://inedo.com/support/kb/1013/hosting-through-iis-instead-of-the-integrated-web-server The only thing I notice from the article is the mention of Classic mode for the application pool - at some point each product was updated to support Integrated mode.

Hello Stijn, This issue is caused by a hidden version of the package: https://www.nuget.org/packages/Swashbuckle.AspNetCore/1.0.0--rc1. I've filed this as PG-1146 and will submit a fix for my co-workers to review.

Tagging would indeed be the solution, now it's clear how we should have been working. Thanks for the fast feedback!

angular-cli gave me problems. It tries to retrieve dependent packages from https://registry.npmjs.org. ( https urls don't works on our dev pc's) At the moment I also configured the server with the feed as my proxy server, so at least that traffic passes over this server for all package handling. (I also have github and such) Tnx for any info you can provide Stijn