Not Working with TFS repositories on VisualStudio.com, but could it? (v1.0.0.1647)

As you guys are aware, you can setup an online TFS account at VisualStudio.com and it's free for the first 5 users. So I've done that for a couple of projects that I wanted to review RedGates SQL Source Control services with.  However when I try and use CI v1.0.0.1647 with my http://jenasysdesign.visualstudio.com instance it gets the following error in the CI log.  I suspect it's a result of the Windows Live authentication approach used by the web site.  Will there be any chance we will get visualstudio.com support into Continua?

Exception: FaultException`1
Message: Error communicating with TFS server, please check details and try again
Stack Trace: at Continua.Modules.Builds.Repositories.RepositoryManager.ValidatePlugin(Repository repository)
at Continua.Modules.Builds.Repositories.RepositoryManager.Validate(Repository repository, Boolean skipPluginValidation)
at Continua.Modules.Builds.Repositories.RepositoryManager.ValidateNew(String name, Int32 pollingInterval, String plugInName, Dictionary`2 plugInProperties)
at Continua.Modules.Builds.Services.RepositoryService.Validate(RepositoryDTO dto)
at SyncInvokeValidate(Object , Object[] , Object[] )
at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)
at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)



This event has been reported 13 times.

Jamie

Did you create Alternate credentials for your account, as the tfs client does not support live authentication :

http://tfs.visualstudio.com/en-us/home/news/2012/aug-27/

I had this working a few months ago but haven’t tested it lately, Dave Sparks is doing some testing with it right now to see if our code is suffering from bit rot

I did test both option, even reset the passwords on the non Windows Live associated account. Got to love the warning on the Visual Studio credential dialog


Some applications that work outside the browser (including Team Explorer Everywhere command line client and the git-tf utility) require basic authentication credentials. Other applications do not properly handle using an e-mail address for the user name during authentication.
To work with these applications, you need to enable alternate credentials, set a password, and optionally set a secondary user name not in the form of an e-mail address. Please note that alternate credentials cannot be used to sign in to the service from a web browser or outside of these applications. Learn more

Well it looks like I must have been testing with the RC version of the client or just have a bad memory(quite likely!). We need to make some changes to support basic authentication… we were trying to do it without binding directly to the 2012 client assemblies but that wasn’t enough. We have a plan and will refactor the code to resolve this, it’s not a lot of work (just need to split some code into separate assemblies), should have it working tomorrow.