For the best part of a week, I’ve been battling with the Visual Studio 2010 Beta 2 extensibility model. I’m happy to report that - finally - I’ve managed to make it bend to my will. ;-)
At this point I’ve decided to fork TestDriven.Net 2.x and 3.x. Going forward, TestDriven.Net 3 will support Visual Studio 2010, 2008 & 2005. TestDriven.Net 2 will continue to support Visual Studio 2008, 2005 & 2003. They will be developed in parallel until the RTM versions of Visual Studio 2010 and TestDriven.Net 3.0 are released. I will then focus my energy on TestDriven.Net 3.x.
With TestDriven.Net 3.0 Alpha, you can expect the Visual Studio 2008 & 2005 support to be stable.
In order to support Visual Studio 2008 Beta 2, I’ve needed to do a number of pretty gruesome workarounds. One of these workarounds involves repainting TestDriven.Net’s command bar button icons each time Visual Studio starts (Beta 2 doesn’t persist them). All previous versions of TestDriven.Net have activated themselves on demand rather than on startup (when Visual Studio loads). This meant installing TestDriven.Net had no impact on Visual Studio startup times.
If you’re sensitive to Visual Studio startup times, it’s still possible to make TestDriven.Net activate on demand in Visual Studio 2010. Simply uncheck the ‘Startup’ box next to TestDriven.Net in the ‘Add-in Manager’. Be warned, however, that TestDriven.Net’s command bar buttons pictures will appear blank until the first time they’re used.
For the ‘Test With > Coverage’ functionality to work with .NET 4.0, you’ll need to install NCover 3.2 or higher (see here). You can also use ‘Test With > Team Coverage’ if you’re running Visual Studio 2010 Premium or higher.
You can download TestDriven.Net 3.0 Alpha from here.