Thanks a lot, I confirm it's working now with v5.2.9

Hello, Sorry for the confusion. For your solution you would need two separate feeds. One for normal package, one for symbols. Thanks, Jason

Hi Chris, You'll need to run the NuGetPackagesV2_SetListed method instead. In order to this, you'll need to mark it as non-internal; this can be done with a simple database query... UPDATE [__StoredProcInfo] SET [Internal_Indicator] = 'N' WHERE [StoredProc_Name] = 'NuGetPackagesV2_SetListed' This will be also be updated in 5.2.10 as PG-1549.

Hello, I think what you are trying to do can be accomplished by adding a restriction for "View & Download Packages" to "any" feed for "Authenticated" users. Then add whatever permission to the API user. Use the Test Privileges button to verify. [image: 1562936601335-92ad03ea-b42d-411b-bd45-e1afd1f6d5fc-image.png] Thanks Jason

Hi Gordon, Looking at the code, it should work if the ReleaseNotes element is within PackageManifest under Metadata. This would be the schema we use: https://docs.microsoft.com/en-us/visualstudio/extensibility/vsix-extension-schema-2-0-reference?view=vs-2019 Thanks, Jason

Thanks very much for the clarification

Hi Jared, According to the docs - It’s currently not possible to mirror another private registry. Only the central Hub can be mirrored. However, we do support connectors to another repository and are nearing completion on a project for docker replication between ProGet instances. Thanks, Jason

Hi Bohdan, For the feed migration please refer to this: https://inedo.com/support/kb/1168/migrating-a-proget-feed As far as Users/Api Keys.. are you using a Built-In user directory only? Thanks, Jason

ProGet does not have the concept of "public" or "private" feeds, you can instead grant the "Anonymous" user certain permissions, including viewing and publishing packages. ProGet Free Edition does not allow feed-level permissions, only system-level permissions. So you can grant "Anonymous" whatever rights you want, just not at a feed-level.

Hi Jared, I am glad it is fixed. I will make a note of how you were able to get it resolved! If you notice anything else, let us know. Thanks, Jason

Hi Larry, Please refer to this documentation for a list of the ProGet license restrictions.

Hello, This documentation may help you determine the best approach for your solution: https://inedo.com/support/documentation/proget/feeds/nuget#nuget Please let me know if you have additional questions. Thanks, Jason

Hi Eyal, What version of ProGet are you using? This was a known issue that should have been fixed in version 5.1 Let me know if this is not that case. Thanks! Jason

Brent, This our public Q&A forum, which is used for software technical support; as such, I've edited your message to remove your company and contact information. That said, we help organizations with compliance-related questionnaires on our products all the time, both sales and post-sales. Please reach out to your Inedo account manager or use our contact form, and send whatever security compliance forms/documentation you are trying to fill out, and we will do our best to advise and help.

Hi, We are still discussing this issue internally. I am wondering if the issue could be with the endpoint.. can you change to /nuget/default instead of /feeds/default/nuget Thanks, Jason

Yes. that is correct. I believe there is a plan to add security into the API.

I had a problem like this (for a different extension tho) and I just restarted the ProGet service, then it worked.

Please refer to this topic for help uninstalling the product.

Hi Andrey You should read carefully this Proget support LDAP auth, but not for the free edition Cdt Philippe

We have a lot of customers who host an instance of ProGet in the cloud, but we do not offer hosting at this time for a number of reasons: better control of infrastructure; you can design your instance to fit for you, instead of in the limited buckets that would be provided choose your own provider; instead of being forced into using whatever cloud provider (or random datacenter) we choose, you can pick the one that you use full control over disaster recovery; no company will care about your data as much as you will, and getting a month free of hosting after losing all of your data probably isn't going to make any of your stakeholders happy As far as how to host a ProGet instance in the cloud, you would be safe simply using built-in authentication and installing it on a public-facing server with only the HTTPS port open. "Anyone" could access the log-in page, and any feeds that you give "Anonymous" access to, but on it's own, ProGet has been pen-tested and will be secure. You could also do any of the following: IP Restrict at the network level use ExpressRoute (a kind of VPN) integrate LDAP (Azure version) instead of built-in authentication sync Azure AD with your AD Those are progressively more difficult to configure, so it just depends on how much effort you want in a POC. Note: we don't recommend regular HTTP, because then a "man-in-the-middle" attack could capture authentication information. But if it's only a POC, maybe it's ok. Finally, some articles for your consideration; A Comparison: Artifactory vs ProGet Azure DevOps and BuildMaster Compared - this is specific to BuildMaster, but most of the points will apply to ProGet