The SOAP-based agent is the IIS-hosted agent, so IIS would need to be enabled. The installer for that agent will automatically set up IIS for you.

Strange, those error messages are coming directly from the TFS SDK. Are you perhaps using hosted TFS? I've found an MSDN thread that might detail why you're seeing that message: http://social.msdn.microsoft.com/Forums/vstudio/en-US/b50ee81b-b2cc-449c-8deb-3d9bafc84d58/access-denied-elastic-build-needs-the-following-permissions-to-perform-this-action-edit?forum=TFService

Actually I was able to reproduce this in our test environment - when the action was rewritten that field wasn't marked as persistent for some reason - one of our devs will publish a new version of that extension in the next few minutes and it will be available from the gallery.

That field is supposed to be required. We will update the behavior of the control to display an error message if no group name is supplied.

We've been making a lot of changes to our SDK during the 4.0 beta period - looks like you found a spot that we missed. I've updated the extension. The Gallio extension (v4.1) should have this issue resolved for you.

Thanks that fixed it

Thanks for the additional debugging information; we now see why this doesn't work. It would appear that NuGet stopped streaming all versions of the packages at some point, and now appends the following at the end of its package search XML... <link rel="next" href="http://www.nuget.org/api/v2/Packages? $filter=tolower(Id)%20eq% 20'ravendb.client'&$orderby=Id& $skiptoken='RavenDB.Clie nt','RavenDB.Client','1.2.2005-Unstable'" /> So, we will need to add support for this as well... I've added this as PG-140, but it's not scheduled for a release yet. If an enterprise (i.e. paying) user requests this, we can expedite it of course.

I ran into similar problems myself with the latest version of ProGet as of 10/22/2013. It seems that the name of the DB has been changed to BuildMaster. I didn't see any ProGet database but there was one called BuildMaster so I followed the directions substituting "BuildMaster" instead of "ProGet" and it seems to have worked.

Submitting here is just fine - the newest 4.0 Beta will do this now, thanks.

That is great.I look forward to the new version. My intial impressions are very good - even though I haven't been able to set up a project.

Downloaded latest version and I am able to make a successful connectiopn to Git but now I am getting: Executing Get Latest Command An unhandled exception occurred while executing this action: System.NullReferenceException: Object reference not set to an instance of an object. at Inedo.BuildMasterExtensions.Git.GitPath..ctor(IGitSourceControlProvider provider, String sourcePath) at Inedo.BuildMasterExtensions.Git.GitSourceControlProviderCommon.GetLatest(String sourcePath, String targetPath) at Inedo.BuildMaster.Extensibility.Actions.ActionBase.ExecuteInternal(IActionExecutionContext context, ExtensionConfigurerBase extensionConfigurer, Boolean resumeNextOnError, Boolean logErrorsAsWarnings) I have not changed anything in the command after upgrading from 3.x . I have removed and readded the Source control provider.

Using the Standard Application template fixed the issue when I put in the Git connection in the deployment workflow.

Hello David! You can add multiple repositories like that in the "Repositories" section when editing the source control provider. When you're editing the provider, enter: http://myserver/svn/ as the Subversion URL, and the repos would be: Relative Repository Path: Repo1 Repository Name: Repo1 If you're having trouble with that, you could always just add multiple source control providers each with their Repository URLs pointing at their own repos.

Feeds_DownloadPackage refers to a user downloading a package from the feed (via NuGet client, VS client, etc.) regardless if it's hosted locally or downloaded from a connector. Feeds_PullPackage refers to pulling a package down from a connected feed into the ProGet-hosted feed. There's a button that does this on the package details page.

The simplest way is: http://inedo.com/support/kb/1001/backing-up-and-restoring-buildmaster It's worth mentioning in the v4.0.1-beta that there is an import/export option for deployment plans (not application configuration yet).

We managed to resolve this - it turns out that the proget feeds were being ignored because the version of proget was not compatible with NuGet 2.7.1. An update to the latest version of ProGet resolved the issue. Thanks for the response though! :)

If the Anonymous user isn't granted privileges for viewing feed and the request doesn't have an auth header then ProGet will return a 401 response for viewing the feed via API. When this happens, NuGet will issue a credential prompt, and resend the request with whatever credentials you enter. Can you do a fiddler trace to see where things are going wrong?

This is not supported, as the comparison report is multiple HTML files; perhaps send a link to the build page itself?

The editors/extensions are sealed, so unfortunately the only pattern available at this time is the "Inherits by Clipboard" pattern. In this case it shouldn't be so bad, since it's a couple-line action+editor.