Connecting Visual Studio 2005 to TFS 2012 and the Team Foundation Service on XP


In a previous post I explained how to connect Visual Studio 2005 to Team Foundation Server 2012 and the Team Foundation Services. This solution works for Windows 7 and 8, but not on Windows XP, since Team Explorer 2012 cannot be installed on Windows XP. There is a workaround for this now through the updated version of the MSSCCI provider for 2010, which now works with Visual Studio 2005 :

The Team Foundation Server MSSCCI Provider enables integrated use of Team Foundation Version Control with products that do not support Team Explorer integration.
This version includes:

  • Updated provider to link against VS 2010 RTM TFS assemblies
  • Improved functionality and performance when used inside PowerBuilder
  • Improved handling of branched solutions in SQL Server Management Studio
  • Decreased number of server prompts
  • Improved error reporting
  • Added support for Visual Studio 2005 to enable VS2005 clients intalled on Windows XP to connect to TFS2012

Creating a Custom Unit Test Generator Provider Plugin for Specflow 1.9


After getting CodedUI Code First and Specflow to play nicely together in the past week, we ran into a few issues with the distribution of the Custom Code Generator Provider assembly to all team members. The SpecFlow binaries installed under a path that contains a random character string and I felt a bit unhappy about the way that other developers had resolved this issue by placing the assembly in the NuGet package folder. Especially since we don't check in the binaries in TFS and package restore might go funcky.

The SpecFlow documentation mentions the new way of registering your Custom Generators through the new configuration item. That is where the documentation ends. But the promise of being able to store your plugin relatively to the test project root looked very promising so I got to work.There is now a SpecFlow.CustomPlugin NuGet Package which will get you started creating your own Specflow plugin. To add the package you must create a new Class Library project using .NET Framework 4.0 or 4.5.

Combining CodedUI Code first, SpecFlow and Visual Studio 2012


Today we tried to combine a number of different test technologies on the latest version of Visual Studio and ran into a few small issues. We found a work around for all of them. So if you want to use the BDD style of Specflow to test the UI of your applications, hold tight.

Make sure you have a version of Visual Studio that supports CodedUI tests (Premium or Ultimate) and install the following add-ons to enable SpecFlow:

Create a new test project (we're using an MsTest based test project, since CodedUI requires that) and use the package manager or the package manager console to add the following NuGet packages:

Most Reading