Sample Files

Proof of concept for running Fitnesse tests via MSTest

Richard — Fri, 18 Jul 2008 21:26:59 GMT

This zip file contains a VS2008 proof of concept solution for running Fitnesse.NET tests via MSTest. The solution contains 3 projects:

A very basic WCF service that is the basis of a call tracking system,in reality there is little to test here, especially as we mock out the data access layer, but this is just a proof of concept.
An assembly that contains the wrapper metjods that the fit test call
A test project that contains the MSTest and associated Fitnesse test.

Sprint Burndown for TFS2008

Richard — Fri, 09 May 2008 13:58:30 GMT

Addresses problems that the sprint burndown chart is blank in TFS2008 when using eScrum.

A modified RDL file that correctly constructs the date values used as measure in the MDX query.

Only tested in UK date format dd/mm/yyyy

Smart Device BlogWriter V1.0.0

Richard — Tue, 29 Apr 2008 10:07:38 GMT

Tfirst release of my BlogWriter for Smart Devices which allows you to post new messages to blog servers that uses the MetaBlog API. My aim was to provide a LiveWriter like application for devices like my HTC PDA.

CCNet MSTest XSLT Transforms for VS2008

Richard — Sat, 05 Apr 2008 12:35:01 GMT

Pair of XSLT Transforms for use with CruiseControl .NET to display detailed MSTEST V9.x (Visual Studio 2008) results in the Web Dashboard.

Note this Zip contains the same pair of files MSTestSummary.XSLT and MSTestReport XSLT available as separate downloads in this site.

MSTestSummary XSLT Tranforms for use with CruiseControl .NET

Richard — Tue, 11 Mar 2008 20:24:07 GMT

XSLT Tranforms for use with CruiseControl .NET to display a summary of MSTEST V9.x (Visual Studio 2008) results in the Web Dashboard

MSTestReport XSLT Tranforms for use with CruiseControl .NET

Richard — Tue, 11 Mar 2008 20:19:06 GMT

XSLT Tranforms for use with CruiseControl .NET to display detailed MSTEST V9.x (Visual Studio 2008) results in the Web Dashboard

TFS WebParts Sample V2.1 (web service to allow 64bit support)

Richard — Fri, 04 Jan 2008 16:16:19 GMT

Readme for TFSWebParts

This project is based upon ideas from http://www.codeproject.com/KB/dotnet/TFS-WorkItemTracking-Web.aspx. These have been pulled apart and re-worked into a pair of webparts for used on any ASP.NET 2.0 hosting service such as IIS or SharePoint

The Visual Studio 2008 solution contains two projects:
•   A DLL with the two WebParts
o   One to do the connection to the TFS server and list work items
o   One to display details drawn from the first
•   A test harness using ASP.NET WebPartZones

The DLL project, as well as building the assembly, will also produce a .WSP file to allow the webparts to be installed as a feature into a SharePoint 2007 server farm. An example batch file with the required STAADM commands to install the feature is also provided.

Usage:
1.   Load the solution in VS2008 (if you need to use VS2005 you will need to recreate the solution file, and point at the right TFS API DLLs, but everything else should work)
2.   Run the test harness project (note as we are using webparts it will have to create a local ASPNETDB.MDF files the first time it runs. The DB contains the config for the webparts so you will see nothing on the first loading until you setup the parameters)
3.   In the test page select the edit mode at the top of the page, then edit the list webpart in WebPartZone1, enter the following:
•   TFSServerURL – the TFS server e.g. http://tfs.mydomain.com:8080
•   TFSWebServicerURL – the TFS wrapper web services e.g. http://tfs.mydomain.com:8080/tfswrapperservice.asmx
•   TFSDomain – the domain used to authenticate against e.g. mydomain
•   TFSUsername – the user name to connect to the TFS server as, we create a dedicated user for this webpart to login as.
•   TFSPassword – the password used to authenticate with (shown in clear text)
•   TFSAllowedWorkItemTypes – a comma separated list of work item types to be listed in the control, must match types in the [System.WorkItemType] field in the TFS DB. Depending on the process template in use the types will vary but as a start in most templates there is a ‘bug’ type.
•   TFSDefaultProject – the name of the default TFS project to select on loading, can be left blank
•   TFSPagingSize – the number of rows to show in the list of work items
•   TFSShowOnlyDefaultProject – if this is set only the default project is listed in the available projects – this means a single TFS user, which can see many projects, can be used for different webpages and the project shown locked down with this parameter
•   TFSUsePaging – set if the list of workitems should be paged
4.   Once this is all done and saved you should be able to a list of projects and workitems in the first webpart.
5.   To wire the two webparts together select the connection mode radio button at the top of the page
•   On the web part in WebPartZone2 select the connect option
•   In the connections zone that appears create a new connection to link the two webparts
6.   Once this is done you should see the detail of any given workitem when it is selected from the list. The problem is you see all the fields in the work item (useful for debugging)
7.   Put web page back into edit mode and edit the settings on the details web part
•   TFSFieldsToShow – a comma separate list of field names to be shown.
•   TFSShowAllField – if checked the TFSFIeldsToShow is ignored

TFS WebParts Sample V2.0

Richard — Wed, 19 Dec 2007 22:23:01 GMT

Readme for TFSWebParts

This project is based upon ideas from http://www.codeproject.com/KB/dotnet/TFS-WorkItemTracking-Web.aspx. These have been pulled apart and re-worked into a pair of webparts for used on any ASP.NET 2.0 hosting service such as IIS or SharePoint

The Visual Studio 2008 solution contains two projects:
•   A DLL with the two WebParts
o   One to do the connection to the TFS server and list work items
o   One to display details drawn from the first
•   A test harness using ASP.NET WebPartZones

The DLL project, as well as building the assembly, will also produce a .WSP file to allow the webparts to be installed as a feature into a SharePoint 2007 server farm. An example batch file with the required STAADM commands to install the feature is also provided.

Usage:
1.   Load the solution in VS2008 (if you need to use VS2005 you will need to recreate the solution file, and point at the right TFS API DLLs, but everything else should work)
2.   Run the test harness project (note as we are using webparts it will have to create a local ASPNETDB.MDF files the first time it runs. The DB contains the config for the webparts so you will see nothing on the first loading until you setup the parameters)
3.   In the test page select the edit mode at the top of the page, then edit the list webpart in WebPartZone1, enter the following:
•   TFSServerURL – the TFS server e.g. http://tfs.mydomain.com:8080
•   TFSDomain – the domain used to authenticate against e.g. mydomain
•   TFSUsername – the user name to connect to the TFS server as, we create a dedicated user for this webpart to login as.
•   TFSPassword – the password used to authenticate with (shown in clear text)
•   TFSAllowedWorkItemTypes – a comma separated list of work item types to be listed in the control, must match types in the [System.WorkItemType] field in the TFS DB. Depending on the process template in use the types will vary but as a start in most templates there is a ‘bug’ type.
•   TFSDefaultProject – the name of the default TFS project to select on loading, can be left blank
•   TFSPagingSize – the number of rows to show in the list of work items
•   TFSShowOnlyDefaultProject – if this is set only the default project is listed in the available projects – this means a single TFS user, which can see many projects, can be used for different webpages and the project shown locked down with this parameter
•   TFSUsePaging – set if the list of workitems should be paged
4.   Once this is all done and saved you should be able to a list of projects and workitems in the first webpart.
5.   To wire the two webparts together select the connection mode radio button at the top of the page
•   On the web part in WebPartZone2 select the connect option
•   In the connections zone that appears create a new connection to link the two webparts
6.   Once this is done you should see the detail of any given workitem when it is selected from the list. The problem is you see all the fields in the work item (useful for debugging)
7.   Put web page back into edit mode and edit the settings on the details web part
•   TFSFieldsToShow – a comma separate list of field names to be shown.
•   TFSShowAllField – if checked the TFSFIeldsToShow is ignored

TFS WebPart Sample 1.0

Richard — Fri, 13 Jul 2007 15:37:53 GMT

A pair of WebParts with test harness and source that allow the display of TFS workitems within ASP.NET 2.0 sites

ThreadApplication sample code

Richard — Mon, 04 Sep 2006 20:33:08 GMT

Sample application showing how unhandled exceptions in background threads can be caught and dealt with