Thank you for the report - it appears the uninstaller is relying on a configuration value that does not exist; the uninstaller will be fixed in v5.0.8. For reference, here is a quick summary of what the uninstaller does: (IIS only) delete ProGet application pool (IIS only) delete ProGet website stop & delete INEDOPROGETSVC and INEDOPROGETWEBSVC Windows services delete %ProgramFiles%\ProGet directory delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ProGet hive from registry (optional) drop ProGet database (optional, SQL-install only) uninstall SQL Server 2016 from "Add or remove programs"

You can uninstall, then reinstall. If you follow KB#1013, and make sure to keep the application pool and websites names as specified, then the installer will detect them next time and upgrade as needed.

This is a "false positive"; https://inedo.com/support/kb/1113/anti-malware-false-positives-code-signing-and-safety-of-inedo-products Please report it to Cylance

Alana, I tested the change and it is working for me with version 5.0.8. Ship it! :)

The issue is related to packages missing SHA1 hashes in the ProGet databases; at some point packages were able to be added without them. We have updated the migration process internally to perform them if they are missing, and this fix will be included in the next maintenance release. Here is the tracking issue: https://inedo.myjetbrains.com/youtrack/issue/PG-1203

The issue is related to packages missing SHA1 hashes in the ProGet databases; at some point packages were able to be added without them. We have updated the migration process internally to perform them if they are missing, and this fix will be included in the next maintenance release. Here is the tracking issue: https://inedo.myjetbrains.com/youtrack/issue/PG-1203

The issue is related to packages missing SHA1 hashes in the ProGet databases; at some point packages were able to be added without them. We have updated the migration process internally to perform them if they are missing, and this fix will be included in the next maintenance release. Here is the tracking issue: https://inedo.myjetbrains.com/youtrack/issue/PG-1203

Add my plus-1 to sorting or searching or filtering by groupname in the UI. As best I can remember, groupname is required by the upload process; at least, i remember it being required by the Jenkins plugin. Maybe i'm wrong/misremembering. But it does make sense for our use case to be able to divide feednames by groups. So it'd be great to have that functionality in the UI.

Hello Leandro, Feeds_GetLicenseUrls hasn't existed since 4.7.0. It's possible that the error you encountered was from a custom extension which is not compatible with 5.0. ProGet 5.0 uses the Inedo.SDK NuGet package instead of the Inedo.ProGet.SDK NuGet package, and loads extensions that end in .inedox instead of .progetx.

hi Markus, you should be able to put credentials in your Connector. Then you should be able to connect.

Thanks Dean, the images are available now.

Thanks for letting us know; we've since fixed the regression in v5.0.7.

That's not a known bug. It's really hard to say; the function should work, and an error should be logged if it's not deleting. You may find errors in Admin > Erros.

Hello Phil, This appears to be a bug where NuGet packages with no stable versions keep their first-uploaded version as the "latest". I've filed PG-1201 with a fix. As a workaround, uploading a version of the package with a version number that does not include a hyphen (with a lower version number than the actual latest version of the package) will make the latest version update correctly.

It looks like this is just an oversight on our part, because the unlisted package is the latest version. I've logged this as PG-1194 and scheduled to fix in a maintenance release.

Hi @mikhael_3947, I have updated our Docker documentation to include this information about using a proxy with ProGet. I have also included more information about insecure registries and using self-signed certificates with Docker registries, Thanks, Rich

Ok, I see that my issue is exactly what is described in https://inedo.com/support/questions/7450. Thanks for the quick reply. I'll update to v5 when it comes out of beta.

If it's an "active" DR (i.e. the servers are running, it's used for testing purposes, etc) then each server would require a license. If it's something like, a snapshot of a server (and isn't running... but could be as soon as production goes off), then you can use the same license. It's similar to a lot of Microsoft (and other vendors) licenses for non-production environments.

There's a bug, PG-1211, that will ship in 5.0.9 that should resolve this API Key issue!

This was caused by a connector that was returning a 500 server error. Inedo might want to look into better handling of these errors.