Posts

I posted yesterday on using Typemock and Microsoft Fakes with SharePoint. After a bit more thought I realised the key thing in using Typemock I found easier was the construction of my SPListItem dataset. Typemock allowed me to fake SPListItems and put them in a generic List then just make this the return value for the Item collection using the magic .WillReturnCollectionValuesOf() method that converts my List to the required collection type. With the Microsoft Fakes I had think about a delegate that constructed my test data at runtime. This is not a problem, just a different way of working. ...

Updated 5 May 2012 Also see my follow up post, this corrects some of the information of faking SharePoint I have done posts in the past about how you can use Typemock Isolator to fake out SharePoint to speed design and testing. The reason you need special tooling, beyond standard mocking frameworks like Rhino or MOQ, is that SharePoint has many sealed private classes with no public constructors. So in the past you only had two options: Typemock Isolator and Moles from Microsoft research. ...

Whilst travelling I had neglected to post about the new release of Typemock Isolator Version 7. This new release extends the range of the product to provide a variety of ‘test support tools’ that help you track down bugs sooner. However, the best new feature for me is that it allows support of historic versions of Isolator, this means you don’t have to upgrade all projects to V7 at the same time. The V7 engine will use the older assemblies e.g. V6 perfectly happily. Make managing build boxes far easier ...

One of the nice new feature of TFS11 is that you get a third option for what to do with your build output Don’t copy output anywhere – good for CI builds that nobody will ever consume, just used to run tests Drop to a UNC share e.g. \server1drops – the default and used 9 times out 10 The new one - drop to source control e.g. $/myproject/drops. The advantage of this new third option is your build agents can place the files they create in a location that can be accessed by any TFS client i.e. in the source control repository. A user no longer needs to be on a VPN or corporate LAN to be able to see a UNC share. ...

It was announced overnight that TEE is now free. What does this mean? It means if you do not have to buy TEE as some extra software if you already have a TFS CAL. This removed a barrier to adoption for developers who work in heterogeneous systems, there is no extra cost to integrate Eclipse as well a Visual Studio with TFS . If you want to find out more about TEE why not come Black Marble’s free webinar I am delivering on the 19th? ...

I recently did a guest post for the VSTS UK Team Blog on Team Explorer Everywhere. On the 19th of March I will be doing a free webinar on the same subject. To register for this event please see the Black Marble web site.

I have proposed a session for DDD South West, why don’t you?

When you install TEE11 Beta in Eclipse you will notice their are two Team Explorer windows Team Explorer 2010 – The old style window Team Explorer – The new VS11 style window This is an artefact of the beta as TEE transitions to the new VS UI. I would recommend you use the new one as this will be the experience going forward. I certainly would not recommend having both open as I have shown in this screenshot ...

Background Whilst at the Microsoft MVP summit there are a number of MVP2MVP sessions, these are similar to DDD style sessions with MVPs presenting as opposed to Microsoft staff. One I found really interesting was one by Richard Banks based on his post on using GIT with TFS. Now this was a usage of source control tools I had not considered, a mixture of Git and TFS (or could be Git to SVN, similar tools are available) ...

Today, as well as the new VS11 Beta bits from Microsoft, the ALM Rangers also shipped best practice guidance to get you started with the beta. This is a project I am very proud to have been involved with. The full details of the supporting guidance shipped can be found here