Code sent! hope this helps. A general rule of thumb... An action that inherits from ProviderBasedAction<T> is designed to run an operation on a single provider (Issue, Source Control, Database, etc). The provider and action plumbing take care of the agent and cross-platform things. If the provider doesn't already do what you want it to, then it's almost always easier to just run a command-line action (CommandLineActionBase), as that takes care of all the process logging and other things.

Well, I guess it wasn't meant to be. I just ran a build and that error came back. I set that flag back to false, ran another build and the error went away.

Are you using IIS or the integrated web server? You may want to try the integrated web server. It's possible an IIS/system-wide setting is overriding some of the configration.

I think so, Gary. Thanks again for the pointers. I'll be sure to ask if I have any more questions. Have a great day! Matthew

The only way to disable the API key is to enable LDAP authentication, which requires the Enterprise edition of ProGet. However, as an FYI, if you do not specify an API key for the feed but are using built-in authentication, the API key follows the pattern "username:password".

This appears to be a problem with the tests themselves. I would take a look at the Cleanup method and see what objects could possibly be null. This post (http://stackoverflow.com/a/10751484/44765) shows the some of the differences with running in the command line MsTest vs. Visual Studio.

Are you trying to create a new instance ("tab") on the config file? If so, and if you're getting that error message, then you'll need to go to "Manage Instances" and click "Show Deleted" in the top of the window. From there, you can undelete the instance.

This has been updated; Oracle Extension 3.1 now supports multiple commands per script. You can update this from within BuildMaster

Hi Joe, Sorry for the poor experience... we do strive for a easy OOB experience, but obviously have only so much control over the underlying platform (IIS). SQL Server is required, but you don't have to install SQL Express; we'll try to clarify the "use your own" option on the installation screen. SQL Express is provided for those who don't have a SQL Server instance to use. We don't have much control over the obscene amount of time it takes, but that's why Lights Out is there... The redirection is a result of some IIS configuration. It could be a LOT of different things, maybe .NET 2 isn't installed/configured/enabled, maybe a global handler is there, etc. This is why we provide the integrated web server, to get started faster. Can you provide some specifics about what IIS you're using? We might be able to provide some pointers on where to start looking...

You're right, at the moment the LDAP provider uses whatever domain it happens to be a part of. We'll put it in the roadmap, but we also offer the ability to "speed up the process" so-to-speak for our enterprise customers via our professional services. If you would be interested in this option for your organization, just send us a message using the contact form (http://inedo.com/contact).

Good idea. We should be able to add this feature in ProGet's next release.

I think I just figured it out. We have some unit tests running which are creating the GUID based XML file in question. I still have to do some more investigation.

It was very helpful.

You need to stop/start the ProGet service (INEDOPROGETSVC) and stop/start the applciation pool (if using IIS).

Thanks a lot. That worked. Your quickness is truly appreciated.

Indexing is currently done in-memory (as opposed to a separate indexing service/database), which can obviously lead to issues like this on very large datasets. I've shot you an email, and we're investigating some options.

I would suggest just disabling your build schedules during the outage period. Maybe at 12:45AM through 1:15AM (or whatever). This can be done through the API methods (BuildSchedules_GetSchedules and BuildSchedules_CreateOrUpdateSCMTriggered), or through a simple SQL Query (UPDATE BuildSchedules SET Active_Indicator = 'N'). We don't have a generic task scheduler built-in to BuildMaster, so you'd want to use Windows Task scheduler to run the enable/disables.

I could certainly try this if you can tell me how. Also would it be easy for me to unistall and go back to the previous functionality, if required? Please let me know what i need to do to test this.

Yes we seem to have an older version. I will update this and let you know. Thanks Chris

That's great news John! (I had a 3 failed builds last night because of this issue)please let me know if you have any questions or if there is any additional information I can provide.