As of 3.1: Active Directory / LDAP Integration Filter Packages by Name & License Load Balancing & High Availability Granular Privileges & Security

In .net, it's usually best to split out your web.config files into multiple files using the configSource option. So, <appSettings configSource="web_appSEttings.config" /> This way, you only need to edit web_appSettings.config when a key changes.

Thank you Steve. i have figured it out. it was downloading the code in different path. Thanks Again

The 0.0 release is merely a setup release, the number for that cannot be set. However, you can cancel that release and simply create a new one and enter in 1.0 for its release number.

We can add a configurable throttle to the timer that triggers a package rescan. In the meantime, you can always trigger an immediate index rebuild by either setting the RebuildPackageIndex setting (under Admin->All Settings) to True, or by restarting the ProGet service.

At some point, the NuGet client started requesting every package version instead of just the latest for updates. The only way to fix this on our end is to add paging/result limiting for feed output. We could hack in a configurable result limit pretty easily which should fix this for you in a maintenance release.

Thanks for the bug reports. This renaming bug will be fixed in the next release. It's only a SQL/stored proc change, so if you would like a patch to fix it against your DB, we can send it to you. We've also fixed the broken link and that will be updated on our next website push. Thanks for letting us know!

It's possible via IIS / appcmd, but the BuildMaster action does not support this behavior.

You can watch the service logs (Admin > service) to see how this "rouge" build is being created. The Scm Watcher will identify how it's specifically searching for changes, and what's causing the trigger to fire.

I believe TeamCity requires that the APIkey is passed in, regardless of if the feed requires it or not. You can just use name:pass as the api key in this case.

Can you be more specific? What do you mean by, "entire database"? The built-in Change Scripts feature will allow you to script an entire database if needed, and ensure change scripts get run once and only once.

Oddly, running the service in interactive mode seems to have solved the problem: the deployment is now complete. I didn't do anything but stop the service and start it interactively, and I didn't notice anything unusual in the output. It did look like it found the action and ran it, as far as I can tell, but didn't say what had been in the way.

Issue #21 opened in Github. Thanks for the comments!

In this case, it sounds like the service account has some sort of enumeration problem with groups. This is not uncommon. As a test, i would suggestto run the ProGet webapp (either in IIS or the hosted web service) with your domain account. And of course, if you do find out specifically what caused this from the groups/permissions side of things, an update would most certainly be appreciated :)

Hi Tod Sorry for that, these are the correct images: ProGet browser https://www.dropbox.com/s/lp00uc995s3h5rl/2014-07-10 15_28_09-GamePlay 2.0.23.png Nuget Package Explorer https://www.dropbox.com/s/ev7bteduhh7hkb3/2014-07-10 17_44_31-NuGet Package Explorer_GamePlay.2.0.23.png The request from Nuget Explorer fails and I assume the same thing happens with the Nuget Package Manager in Visual Studio: Request: GET http://srvsedevtfs01:81/nuget/default/FindPackagesById()?$orderby=Published%20desc&$select=Id,Version,Authors,DownloadCount,VersionDownloadCount,PackageHash,PackageSize,Published&id='XXXXXX.XXXXXX.XXXXXX.GamePlay' HTTP/1.1 DataServiceVersion: 2.0;NetFx MaxDataServiceVersion: 2.0;NetFx User-Agent: NuGet Package Explorer/3.8.0.0 (Microsoft Windows NT 6.1.7601 Service Pack 1) Accept: application/atom+xml,application/xml Accept-Charset: UTF-8 Host: srvsedevtfs01:81 Accept-Encoding: gzip, deflate Response: HTTP/1.1 404 Not Found Cache-Control: private Content-Length: 6505 Content-Type: text/html; charset=utf-8 Server: Microsoft-HTTPAPI/2.0 X-AspNet-Version: 4.0.30319 X-UA-Compatible: IE=edge Date: Fri, 11 Jul 2014 14:30:39 GMT <h1> Request handler not found (404) </h1> <div class="subH1"> An unexpected error has occured while processing your request. </div> <h2>Error Details:</h2> <div style="overflow: auto; height: 100px; border: 1px dotted #A00; padding: 10px; color: #A00;"> /nuget/default/FindPackagesById()?$orderby=Published%20desc&amp;$select=Id,Version,Authors,DownloadCount,VersionDownloadCount,PackageHash,PackageSize,Published&amp;id=&#39;XXXXXX.XXXXXX.XXXXXX.GamePlay&#39; does not map to any handlers. The URL may have been entered incorrectly or linked to from an old reference. </div> <h2>Why am I seeing this page?</h2> <p> You were taken to this page because ProGet encountered an error without a specific or known resolution. </p> <h2>What else can I do about this?</h2> <p> Hopefully the error message above is helpful in determining what went wrong. </p>

Not possible currently, but something we could definitely add - I'll put an issue in for this.

Only the single agent port is required to be open. As a workaround, if you have BuildMaster database access, you can just set the status of the particular server to FORCE. If you have a custom extension, you could write a quick custom recipe that can do it as well - just implement the IServerRecipe interface for a RecipeBase object. You can find out how this works in the Creating an Auto-Deploying Custom Extension Application tutorial which contains a downloadable example project containing example recipe code.

You could try calling the stored procedure directly via the SQL API: DECLARE @B VARBINARY(MAX) SET @B = CAST('yourname' AS VARBINARY) SET CONTEXT_INFO @B EXEC Applications_PurgeApplicationData @Application_Id or view it in SSMS to see the actual SQL.

This is a known issue (BM-1546) for BuildMaster v4.3.8 and will be resolved in v4.3.9.

Thanks for this! We also use ProGet for internal assemblies and having symbols readily available through the NuGet package saved me from having to hack something together so we could have easy access to the PDBs.