In 2008 I wrote a post Running Fitnesse.NET tests using MSTest.  Recently I had need to us this technique on a VS2010 project, and as is so often the issue the code that worked then does not seem to work now. All I can assume is that the Fitnesse API had altered, but I thought I was using the same assemblies!

So I …

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 …

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 …

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 …

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

I recently tried to use Typemock Isolator inside a ASP.NET page load event, to fake out some SharePoint SPLists e.g.

protected void Page_Load(object sender, EventArgs e)
{
     SPSite fakeSite = Isolate.Fake.Instance();
     ……..
}

This has worked in the past but using VS2010RC and Isolator 6.0.1.0 it failed.

• If …

Whilst upgrading a single server instance of TFS 2010 Beta2 to the RC I got a TF254024 error. This occurred at the point in the upgrade wizard where it tries to list the databases available to upgrade.

The reason for the error was the account I was logged in as (the domain administrator in my case) did not have rights …