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. So I tried to create the DB TFS_RC_ABC manually and pointed the TPC create process at this. It passed the verify but I then got a ...

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 .NET 4, there is no option to build with an older runtime. I suffered this problem when trying to do some development where I hosted a webpart that make calls into SharePoint (that was faked out with Typemock Isolator) inside a ASP.NET 4.0 test harness ...

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

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 running VS2010 as Admin I got the error “Could not load file or assembly ‘TypeMock, Version=0.12900.25133.13153, Culture=neutral, PublicKeyToken=37342d316331342d’ or one of its dependencies. The located assembly’s manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)”:“TypeMock, Version=0.12900.25133.13153, Culture=neutral, PublicKeyToken=37342d316331342d”}" If running as a non admin user I got the error “Attempted to read or write protected memory. This is often an indication that other memory is corrupt.” Typemock Support told me that I needed to edit the Typemock Isolator’s namespaces.dat file (in its programs directory), this is the file that lists valid test runners. I needed to add WebDev.WebServer40.exe to this file as this is program that makes the call to Isolator to do the faking. ...

Our new Internet line has now been commissioned fully and hopefully any problems you may have had accessing my blog via the blackmarble.com or co.uk domains should be over.

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 on the SQL instance to see any TFS DBs. Once this was sorted, by granting owner rights to all the TFS DBs, all was OK. ...

Updated 25th Mar when I found I have three sessions I have just heard that I had two three sessions accepted for the Norwegian Developers Conference. They are: Putting Some Testing Into Your TFS Build Making Manual Testing a Part of Your Development Process Developing Testable Web Parts for SharePoint. So off to Oslo, never been there before, looking forward to it already

For some reason that is beyond me now I did not setup my Lab Manager test system to be a VHD boot. So before installing the 2010 RC version I decided to P2V this system (on the same hardware) to make backups easier whilst testing. All seemed to go well I used IMAGEX to create a WIM of the disk Created an empty VHD Used IMAGEX to apply the WIM to the VHD Formatted the PC with a default Windows 7 install Added a VHD boot Windows Server 2008R2 to the PC, tested this all booted OK Replaced the test VHD with my own and rebooted …. and it just went into a reboot cycle. Pressing F8 and stopping the reboot on error I saw I had a “c00002e2 Directory Services could not start” error. I managed to get into the PC by pressing F8 and using the AD recovery mode (safe mode did not work). After much fiddling around I eventually noticed that my boot drive was drive D: not C: as I would have expected. My VHD and parent drive had reversed letter assignments. So when the AD services tried to start they look on the parent Windows 7 partition (C:) for their data and hence failed. ...