TestDriven.NET by Jamie Cansdale

Zero Friction Unit Testing for Visual Studio .NET

  • Reflector Add-In Resurrection

    You must have been hiding under a rock if you haven't heard about the new version of Lutz Roeder's .NET Reflector by now. With its support for generics, loading any version of mscorlib (including 2.0 and Mono) and the refreshing of assemblies you're in for a treat! This means all of the frustrations faced by my original Reflector Add-In are gone.

  • One for the brave...

    devenv nunitaddin.sln /build Debug
    sln2wxs nunitaddin.sln /config Debug
    candle nunitaddin.wxs
    light nunitaddin.wixobj
    ren *.msi NUnitAddIn-0.6.207d.msi dir *.msi 01/05/2004 15:09 845,312 NUnitAddIn-0.6.207d.msi 1 File(s) 845,312 bytes 0 Dir(s) 2,674,440,704 bytes free

  • Parsing a Solution File

    There's a new challenge up at Code Blog.  This time the tests are for something a little more real.  The aim is to parse a Visual Studio SLN file.  I admit to having a vested interest in some code to do this.  I am sick to death of poluting my test code with explicit knowledge of where project output directories are located ('bin\Debug' or whatever).  I really want to reference my project directories by name.  For example, 'Projects.Find("MyProject").BaseDirectory'.

  • Assembly References

    I've added the ability to add assembly references when compiling with Code Blog.  Something that threw me is the strong name key used to sign the 'System' and 'System.Web' assemblies are different!  To make life easy for you I'm now using LoadWithPartialName.  To reference the correct version of 'System.Web' you can just do "System.Web, Version=1.0.5000.0".