Based on the URL -- you must have created a Universal Packages feed. You'll need to create a NuGet feed.

Hello; Inedo.com currently seems to only communicate over TLS1.0; I don't have a timeframe for when that will be upgraded, but I want to add that we don't have any secure or sensitive information on inedo.com anyways. In the case of LDAP, it seems to me that there is some sort of issue with the LDAP code mapping your username. AD configuration can be very complicated I'm afraid, and it will involve a bit of back-and forth, with sharing potentially sensitive or company-identifying information. When you search for a user in ProGet, you will see a log of the domains, etc., being searched. Ifyou can publish that to a ticket, then we can investigate further.

hi Keith, We definitely plan on having an offline process, and welcome your feedback on it. You can read a bit about how the hub works (it's in beta, so please forgive the rough docs). Specifically, check out "Configuration and Offline Installs": https://inedo.com/support/documentation/proget/installation/hub/inedo-hub The Inedo Hub wraps Romp (more coming soon on that), so you could also use that to install ProGet as well, as a command line process. Does that help?

This particular error (the 500) will be fixed with PG-1313

Thanks Dean, I did a fresh install. The new settings are so minimal that I'm not sure people will notice the change. Crashes after the first one are silent, as before, making the user restart the service by hand and think "ProGet flaked out". What do you think about resetting the fail counter every few days? About using the "run program" hook to report crashes? Does Inedo automatically get crash reports? Thanks for your help.

Hello; please fill out the contact form, and we will be able to you via email.

We don't have any guides on this integration specifically, but the usual situation is that TC can't authenticate. The easiest thing to do is to allow anonymous publishing to the feed, but not overwriting. Otherwise, you can try to get the authentication to properly work, which typically involves sending username/password or configurating an API key properly.

I'm afraid Linux doesn't support Windows Integrated Authentication. As a work-around, you can create a second site in IIS that points to the same path, but doesn't have Windows Integrated Authentication enabled.

We've narrowed down the issue. It seems that the service user that ProGet is running with cannot see all the members of the LDAP groups. This can be fixed by changing the user to one that can see all members of the LDAP groups through this process: https://inedo.com/support/kb/1077/configuring-your-inedo-product-to-run-as-a-windows-domain-account

It was my reverse proxy (apache). I had to set AllowEncodedSlashes to On. Problem solved.

I see, that's an interesting idea. It seems like some sort of auto-generated documentation of sorts? I don't know if ProGet is the place for that data, but we don't have a feature to store such doumentation at this time. So, maybe you could auto-post it a documentation wiki of sorts and use the "Project URL" property to link to it?

ProGet does not have a "pin version" feature, though it has been requested in the past. Instead, you may just want to create an "archived" feed, and promote packages you want to "pin" to that.

Sure, here they are: ProGet License Agreement Security and Access Controls

I'm afraid we don't have an ETA at this time; we're currently focusing on Debian and PyPi feeds for the moment, and hope to move towards Composer later.

Hi @ReginaldD, did you manage to bulk-delete packages from your server using inedo API? Cheers,

Hello; just to let you know, the Inedo ProGet Plugin for Jenkins has been updated, and may work better. Have you had an progress onthis otherwise?

Well maybe it could be useful to at least integrate into the configuration of the application. This would be a good option if you'd choose that you don't want it to be found in online search results.

You'll want to push a "combined" symbols package to http://🚫/nuget/feed-name - the symbols endpoint is for downloading extracted symbols only. Check out the guide we have at Symbol and Source Server docs for more info