Noticed this is already reported https://inedo.com/support/questions/8463

Actually, the API isn't really any faster or slower. If you find it faster to query NuGet.org's "v3" API endpoint, the reason is that it's a static index hosted on a massive Azure server farm. Your ProGet server is considerably less powerful. In addition, ProGet has connectors, authentication, package filtering, etc., and it would never be feasible or useful to generate a static index like NuGet.org does. However, it is on our 2019 roadmap to implement this API, possibly as a new feed type or as an alternate API endpoint for an existing feed. But even so, if you need performance, you may still need likely need to stand up several ProGet servers in a load-balanced manner. See How to Prevent Server Overload in ProGet to learn more.

Try stopping the service before running the installer, then it should work.

Hello; thanks for the report, this has been filed as PG-1229

The "remote icon" means that there is a package entry in a remote server. If you're continuing to see it, then it may take a little bit for the connector metadata (in memory)cache to be cleared. You could always stop/start the webservice, and then this will go away.

Please have your colleague follow the instructions in Source and Symbol Serving; it's easy to miss one small detail, and then in this case, it won't work.

You can use the NuGet API for this purpose; https://docs.microsoft.com/en-us/nuget/api/package-publish-resource#delete-a-package Make sure to replace the feedurl with your ProGet Feed's API Endpoint URL (it will start with /nuget, not /feeds)

From what I understand "portable" PDBs were introduced with dotnet core. This is some legacy code that is written in vb.net and is using the full .net framework. As far as I know it is just a traditional windows PDB.

We've been holding to v5.0.6 because it appears this issue is still open and was introduced (as far as we can tell) in 5.0.7: https://inedo.com/support/questions/8240 Has this been addressed in the latest build for linux on docker?

Please share the full stack trace / message under Admin > Message Center.

They fixed an issue using API keys in the latest version 5.0.9 - https://inedo.myjetbrains.com/youtrack/issue/PG-1211

So no version of 5.x is usable when pushing to the feed? I was hoping to leverage v5 because of it's SemVar 2.0 support.

Hello Thomas, I've filed PG-1223 to fix the UI sending you to the wrong URL and promotion trying to load the package from the wrong filename (the name contains the build metadata, but the promotion code doesn't add it on the source feed).

Hello Andre, The version number you posted is indeed a valid SemVer2 version number. If you go to the Manage Feed page for the NuGet feed, is there an orange button near the top of the page that says Migrate? If that button is present, the feed is not marked as supporting SemVer2.

There isn't currently, but there will be soon! Please see PG-1221 I can't imagine any reason at all this wouldn't be done, and it can go it the next maintenance release assuming it passes code review etc! Thanks much for the specific suggestion!

Hello Emil, If source or symbol stripping is enabled on the NuGet feed, the package you download will be dynamically created. If you add a query parameter ?includeSymbols=Y in the package request, ProGet will give you the original nupkg file, which should have the SHA512 sum from that field.

The installer sets it to: SQL_Latin1_General_CP1_CI_AS

See my response here. In summary, it's not a valid SemVer2 version number because it contains 4 parts before the hyphen, and it's not a valid legacy version number because it contains a . after the hyphen.

The Jenkisn Plugin can only be used to upload Universal Pakages to a Universal Feed. You'll need to use Powershell-Publishmodule command to publish to ProGet.

Hey Ben, I've updated my nuspec: <?xml version="1.0" encoding="utf-8"?> <package xmlns="http://schemas.microsoft.com/packaging/2010/07/nuspec.xsd"> <metadata> <!-- Required elements--> <id>test</id> <version>1.0.0+meta</version> <description>test</description> <authors>tester</authors> <!-- Optional elements --> <!-- ... --> </metadata> <!-- Optional 'files' node --> </package> When I upload a package created from this nuspec, I get this result