Everything you want to know about Visual Studio ALM and Farming
Brian Harry is a Microsoft Technical Fellow working as the Product Unit Manager for Team Foundation Server. Learn more about Brian.
More videos »
I want to appologize for the problems people have experienced with strong name signing and the updated MSSCCI provider. We should not have posted it with a manual work around of disabling strong name signing for the test key. Although many developers will already have it disabled for testing their own code, it's generally a bad practice to require that. We are working on remedying that problem and plan to release a new build in the not too distant future that will no longer require this.
In the mean time, if you choose to use the current build, you will need to disable the test strong name key verification and here are some details on how to do that:
Thanks for your patience with us.