When you use the InvokeProcess activity, as I did in my Typemock post, you really need to setup the logging. This is because by default nothing will be logged other than the command line invoked, not usually the best option. There are a couple of gotta’s here that initially caused me a problem and I suspect could cause a new user of the 2010 build process a problem too. The first is that you need to declare the variable names for the InvokeProcess to drop the output and errors into. This is done in the workflow designer putting the variable names in the relevant textboxes (there is no need to declare the variable names anywhere else) as shown below. Use any name you fancy, I used stdOutput and stdError. ...

You may have noticed that Microsoft have had another burst of renaming. The tester’s tool in VS2010 started with the codename of Camaro during the CTP phase, this became Microsoft Test & Lab Manager (MTLM) in the Beta 1 and 2 and now in the RC it is call Microsoft Test Manager (MTM). Other than me constantly referring to things by the wrong name, the main effect of this is to make searching on the Internet a bit awkward, you have to try all three names to get good coverage. In my small corner of the Internet, I will try to help by updating my existing MTLM tag to MTM and update the description appropriately. ...

A bit a a double question here, physically I have been at the the MVP Summit in Redmond, having a great time with my fellow “Team System” MVPs and the Microsoft product group members. But my blog has also been on and off all week, so I guess you could say my online presence has been away. This is because [Black Marble has moved office](http://www.blackmarble.co.uk/SectionDisplay.aspx?name=News&title=Black Marble has relocated to Woodland Park) and our blog server has had intermittent connectivity, which hopefully should be resolved soon. ...

I will be joining Iain Angus (Black Marble) and Giles Davies (Microsoft) this week at Microsoft’s Offices in Edinburgh to [present on Application Life Cycle Management](http://www.blackmarble.co.uk/events.aspx?event=Microsoft and Black Marble present Visual Studio 2010 and Managing the Application Lifecycle with Team Foundation Server). We will be looking at how VS2010 can help project managers, architects, developers and testers to build better solutions. There are [still a few places left](http://www.blackmarble.co.uk/events.aspx?event=Microsoft and Black Marble present Visual Studio 2010 and Managing the Application Lifecycle with Team Foundation Server),I hope to see you there if you are in the area. ...

If you look on Google Groups you will find the start of a thread trying to organise some AltNet Beers session in Leeds, only the same lines as the London, Bristol etc. events. There appears to be no date set as yet, but keep an eye open, they are a great way to meet like minded people.

A late reminder but tonight is the monthly Agile Yorkshire meeting. This month is an open floor meeting with short presentations from members. Currently the planned subjects are: REST and OpenRasta Silverlight F# Thoughts on Test Driven Development practices Behaviour Driven Development Hope to see you there, usual place usual time (Victoria Hotel, 28 Great George St, Leeds. See here for directions, 7pm)

I have got round to watching Peli de Halleux’s presentation on testing SharePoint with moles from the SharePoint Connections 2010 event in Amsterdam, very interesting. This brings a whole new set of tools to the testing of Sharepoint. I think it is best to view the subject of this presentation in two parts Pex and Moles, even though they are from the same stable; Moles being produced to enable Pex. But rather than me explaining how it all works just watch the video. ...

I was doing some work today where I needed to fake out a SPWeb object. No problem you think, I am using Typemock Isolator so I just use the line var fakeWeb = Isolate.Fake.Instance(); But I got the error Microsoft.SharePoint.SPWeb.SPWebConstructor(SPSite site, String url, Boolean bExactWebUrl, SPRequest request) Microsoft.SharePoint.SPWeb..ctor(SPSite, site, String url) eo.CreateFakeInstance[T](Members behavior, Constructor constructorFlag, Constructor baseConstructorFlag, Type baseType, Object[] ctorArgs) eo.Instance[T](Members behavior) (Points to the SPWeb web line as source of error) TypeMock.MockManager.a(String A_0, String A_1, Object A_2, Object A_3, Boolean A_4, Object[] A_5) TypeMock.InternalMockManager.getReturn(Object that, String typeName, String methodNAme, Object methodParameters, Boolean isInjected) (Points to line 0 of my test class) ...

I have at last worked all the way through setting up my portable end to end demo of testing using Windows Test and Lab Manager. The last error I had to resolve was the tests not running in the lab environment (though working locally on the development PC). My the Lab Workflow build was recorded as a partial success i.e. it built, it deployed but all the tests failed. I have not found a way to see the detail of why the tests failed in VS2010 Build Explorer. However, if you: ...

I have been looking at TFS 2010 Lab Manager recently. One problem I had was that using the sample code from the Lab Manager Blog Walkthru the building of the CALC ASP.NET web site failed on the build server, I got an error ASPNETCOMPILER: error 1003 The directory ‘c:build1LabWalkthruCalculator –BuildCalc’ does not exist. and the build service was right it didn’t exist; it should have been ‘c:build1LabWalkthruCalculator –BuildSourceCalc’. This was due to a problem detailed here. The Solution file had the wrong path in the Debug.AspNetCompiler.PhysicalPath property. It was set to “..Calc” when it should have been “.Calc”. Once this was altered the build could find the files. ...