Posts made by michal.karpinski_1079

I unlisted a package we created internally thinking it would no longer show up when browsing packages in Visual Studio or in the Package Manager Console.

We have the following versions:

• Package v2.0.6 (unlisted in ProGet web UI)
• Package v2.0.5
• Package v2.0.4
• etc

In the ProGet web UI, v2.0.6 is not shown any more. But when searching for the package in Visual Studio (either in manage packages or using the Package Manager Console), the unlisted package is still returned as the top result.

Is this by design? I thought that unlisted packages were ommited from these results and only available if one had the exact version number of the unlisted package?

Product: ProGet
Version: 4.8.9

We have an internal ProGet feed that acts as a connector for nuget.org. For some packages, however, we get errors restoring packages when using the ProGet endpoint. Using nuget.org directly works fine.

I've narrowed the problem down to the following request being made by nuget.exe:

Restoring packages for .NETCoreApp,Version=v2.0...
2018-01-03T11:38:36.0086973Z            CACHE http://proget/nuget/Ekstern/FindPackagesById()?id='Swashbuckle.AspNetCore'
error NU1101: Unable to find package Swashbuckle.AspNetCore. No packages exist with this id in source(s): Ekstern

Performing the same query against ProGet using Postman confirms what nuget.exe reports - no metadata is returned.

Using the ProGet web UI I can find the package with no problems in the feed. To work around the problem, I have to pull the package to ProGet using the web UI. Only then will FindPackagesById return the package ID and version.

I'm guessing this is a bug? Or have I misunderstood something?

Product: ProGet
Version: 4.8.9