Uncategorised

I my previous post I discussed how the DB label was not used for TPC Dbs in 2010. As I was working on a setup where a central SQL box was the DT for two virtualised TFS AT instances, I therefore needed to create my TPC databases manually if I wanted TPCs of the same name on each TFS instance. I won’t go over the [old post again](I had to create a TPC Dbs manually ), but in essence I was trying to create a TPC with the name ABC on a TFS instance with a database label of RC....

When I said will our internet bits were back I was not quite right. I had forgotten that I had not re-pointed m own richardfennell domains to put to my blog. These are now done, so I hope all search results to my blog should resolve OK.

If your application has a dependency on an assembly built in .NET 2 you will see the error below if you try to run your application when it has been built in.NET 4. Mixed mode assembly is built against version ‘v2.0.50727’ of the runtime and cannot be loaded in the 4.0 runtime without additional configuration information. This can be important in VS2010 testing, as test projects must be built as ....

Found out something I did not know today, the TFS 2010 database label is only used for the server’s own primary configuration databases not for the DBs for the TPC it creates. For example on a 2010 RC install with the database label was set to RC during the installation. When I try to create a new TPC (called ABC) it tries to create a Db named TFS_ABC, even though the database label for TFS server can be seen to TFS_RC_ on the admin console and the instance’s primary databases are called TFS_RC_Configuration, TFS_RC_Warehouse and TFS_RC_Analysis....

My Team Build 2010 custom activity for Typemock Isolator is now available at http://site.typemock.com/add-ons/. It is packaged as a zip which include all the source and a compiled assembly as well a document detailing usage and why the solution is constructed as it is. Hope you find it useful