We consider v2 and v3 to already be semi-retired, which means that we will provide very limited support to users who have not yet upgraded, and will provide assistance in performing upgrades. However, we will no longer ship maintenance releases, patches, or other changes for those versions.

Hi, i am upgrade my old installlation 5.0.10 to Proget 5.1.20.7 today. And i run into the same issue. My Port customization has been overwritten in the C:\ProgramData\Inedo\SharedConfig\ProGet.config. I fixed it manually and now it works.

Thanks for the suggestion. We've filed this as PG-1412 for inclusion in a future maintenance release.

These will be included in the next maintenance release as per this issue: PG-1406

Thanks, that helped a lot. I removed some connectors to myget.org and it's getting faster.

If you're finding that you're having trouble with specific versions, please provide a detailed reproduction case with a specific package, and the specific steps you took; this way we can investigate it.

Ok, thanks. I understand what you're saying now.

Hi Dean - apologies, other priorities came up and I lost track of this. I see your point regarding those extensions. I would be interested in getting our custom extension running if possible, so yes if you can contact me directly that would be great

These are available on the All Versions page: https://inedo.com/proget/versions

Could this be related to Quirks mode? https://inedo.com/support/documentation/proget/feeds/nuget#legacy

I'm not sure if I totally understand the question, but packages are designed to be immutable, and as such you really can't "update" them. You can delete or overwrite a package if you have permissions, but it's inadvisable and you should not make this part of your workflow. In addition to being against the fundamental package workflow/design guidelines, packages are cached by clients like Visual Studio, and won't see a "new version" of a "version" of a package.

There are no changes in ProGet that would cause this. Most likely the package file is invalid, something is cached, you're using the wrong URL, etc. If you can provide a very specific reproduction case using a new (empty) feed, and a specific set of packages that, when uploaded in a specific order, cause this behavior, we can investigate it further.

Ok, recursive search enabled, it still doesn't assign the rights based on my group membership. I'll create a ticket with a few screenshots, I'd rather not post names of our internal groups on the wider internet :)

So between running the 'ProGetInstaller.exe' after deleting keys and directories... didn't realize the unpack directory gets recreated each time. So once I knew I deleted the 'unpack' directory... I never checked again for it. Now that I removed that directory and ran 'ProGetInstaller.exe'... looks like I can now install the application. Yes something simple and stupid. Thank you all for you help!

Please refer to KB#1090 for how to grant service control permissions and avoid this service control error. If you're getting a 404, then you're not using the proper API Endpoint URL. I'm guessing, you're using whatever URL in your browser? Please refer to this tutorial for how to configure this in Visual Studio.

You need to create an API in the ProGet UI; API Access and API keys

Your server is configured to disable the use of .NET's MD5 processing libraries, which means ProGet cannot read or write Maven index files. You can disable this at the server level: https://www.schneider-electric.com/en/faqs/FA282064/ You can also edit the configuration file; https://docs.microsoft.com/en-us/dotnet/framework/configure-apps/file-schema/runtime/enforcefipspolicy-element

This is a property of the service. Just go to "Services" on your computer, edit the service, and change the Auto-recorvery options.

Hi Alana, Thanks so much for the update and the workaround solution. I'll be sure to upvote the linked issue. Best, Michael

This was a result of a imcompatable script with 2005, but it has been fixed as of 5.1.11. We are also displaying warning if you're using unsupported version of SQL