See: http://inedo.com/support/questions/4487

If that action is causing issues with that, to get you running again just replace it with a command line action with the same arguments from the BuildMaster log, then add your reference paths that way. As for the actual question, I believe if you specify the same property twice, it concatenates them.

Connectors can only be filtered by ID, so you'll have to rely on the client to filter by pre-release versions. You can clear the cache on the Manage Feed page.

Well, strictly speaking, it doesn't work as advertised, because I was missing the $format. This gives the desired result. http://progetna11.atlas.cm.com/nuget/branch/Packages()?$format=json&$filter=Id eq 'Web'

Hi, upack is the command line client for ProGet universal feeds. We will soon have it available to download from Chocolatey and Inedo.com, but for now you can find it directly at this URL: http://cdn.inedo.com/downloads/proget/upack1.0.0.zip

I'm afraid we don't have that tutorial yet; but we'd like to soon!

hi, i think this is not an nuget or chocolatey specific thing. proget has to render the *.nuspec infos. like uget gallery https://github.com/NuGet/NuGetGallery/issues/2280 regards sundayout

Not currently, it's just per application level right now. We will definitely consider adding that in a 5.x release!

Thanks. Once I gave the anonymous user delete package privileges, and passed the API key as a header, I was able to accomplish this. However, I find it odd that a successful DELETE call returns nothing.

ProGet is the server, so it just hosts your private packages. If you want to push something to a different feed, use the -Source ... argument in the nuget.exe client. Connectors for NuGet are simply a convenience that make it easy to cache nuget.org packages and provide a single endpoint to download them.

Ya thats goes well! thanks alot. Its working now.

There currently is no transform for this and it's unlikely we will add one.

This is correct, bower packages are not packages but simply URLs that point to a git repo. The git repo is the "source" of the package so without continually syncing the entire git repo it wouldn't be very useful. We may in the future add this (so no outside repos are requested similar to npm's and maven's indexing), but it's a ways off.

You can install a separate website in IIS that points to the same home directory, which supports forms authentication, then use that separate URL for npm & bower. With a separate IIS site, upgrading won't touch it so it will upgrade as per normal with the installer.

This is a bug in the Release_PurgeReleaseData stored procedure that was fixed in a later version. You can patch it by editing it and removing these lines: /* 2c) Configuration */ DELETE [ChangeControls] WHERE [Application_Id] = @Application_Id AND [Release_Number] = @Release_Number NOTE: make sure it's the 2c) line and the 2 following you delete... the 2d) one is correct. (The delete from the ChangeControls table is in there twice for some reason, which is the cause of this bug.)

Hi Just wondering if this issue was resolved ? Pod

Hi Riko Was this issue resolved for you I am facing similar issues with ldap in my company.

You can visit this directly (it'll look a bit strange since it's designed to be a modal page): http://{proget-server}/administration/security/users/change-password Apparently you're correct that the link to that is missing, it's supposed to be in the dropdown beneath the user icon - we'll add it back in the next maintenance version.

This means that packages with the same ID/version are being added to the feed, the only way to prevent this is either grant the privilege as described or don’t push the same unique package more than once.

Thanks for the report, we will investigate this further. We already know of an issue where there is disparity in the UI if the service is in the process of stopping/starting.