TestDriven.NET by Jamie Cansdale

Peter Provost - If the focus is on the Output window, and you use a hotkey to launch the addin, you get an output message that says, "Unknown window vsWindowTypeOutput". It sure would be nice if it could find the topmost open editor and use the first test class in there.

The final release is getting close. This last two weeks I've been fixing bugs and tackling issues I kept putting off. A lot a work has gone into getting the installer right. Getting an add-in to install and uninstall consistently for all versions of Visual Studio .NET is a minefield!

I'm now using MSBuild and WiX for all of my active projects. I ended up with a few VS2003 solutions that I didn't want to convert to VS2005/MSBuild format for one reason or another. It is a pain keeping Windows Forms applications compatable with .NET 1.x when editing using VS2005. I also wanted to be able to compile NUnit for .NET 1.0 using the VS2003 solution strait out of SourceForge.

For some strange reason FTP uploads are only working from one machine on my network.  The working machine is running WinXP SP1.  All of the other machines are WinXP SP2 or Windows 2003 Server.  I've disabled the windows firewall on all of these machines (I'm running behing a NAT router) but still no joy.

Here is the lazy way to update to the latest version of TestDriven.NET (AKA NUnitAddIn)

As some of you have already noticed, the last version of NUnitAddIn expired today.  With impeccable timing my Subversion server ran out of space and 'wedged'.  Luckily I do have backups and local versions on various machines.  To cut a long story short, I have been recovering that rather than getting out a new version for the last 24 hours.