TestDriven.NET by Jamie Cansdale

The Roman Kiss Phenomenon
A few days ago, Roman Kiss presented the world with the Remoting Probe.
This is just the latest in a line of articles he's published on codeproject.com.

Don has just got a WordML to XHTML transform working.  This means I could create a WebDAV front end to my blog and edit entries directly in Word!  Just having the Word spell checking facility makes this worth doing for me.  Is there any chance you send me that XSLT?  ;)

Prototyping addins can be frustrating. If you don't fancy learning VB.NET just to write macros, you're forced to work with a full blown addin. This is anoying if all you want is a quick spelunk inside the VS automation model. This is why I've added another test target. If you select 'Run With... VS.NET', your tests will run inside the current VS.NET process. I've made the DTE object accessable using AppDomain.Current.GetData("DTE").

Nauman Leghari writes "I am looking for an addin which can convert code to html from the VS.NET IDE".  I've been thinking about this recently too.  It would be easy to adapt the NUnitAddin code to do this.  Look for AddControl("Code Window", 3) in the source.  You could use the SgmlReader to filter the code (after copying it to the clipboard).  It does copy as a kind of HTML, but with lots of horrible Office and style tags (look the the HTML of any if the snippets I have posted).

The good news is the the first major release of NUnitAddin for quite some time is out (version 0.5 build 105).  The bad news is that it only works if the .NET Framework 1.1 is installed.  It works with VS.NET 2002 and 2003, but only if 1.1 is there.  So far the issue has defeated me.  It looks like a NullReferenceException is being thrown deep in the bowels of .NET Remoting.  The exception is being thrown by the NUnitAddin.TestRunner.Server program.  If anyone can find the problem I would be hugely grateful.  You can set a breakpoint in the source and use the new 'Run With... Debugger' feature to step into the offending code.  Good luck... ;)

.

Scott made a post about the future of .NETWeblogs and a possible moderated feed.  I agree the main feed is too noisy.  There's just too much stuff.  If I read every single post I wouldn't get any work done.  I don't know if you saw, but I posted about a possible way to tackle the problem...  Blogmarks

Duncan Mackenzie commented about a command line switch parser he found. Has anyone thought of doing command line parsing using (my current favorite class) the XmlSerializer? The code that follows can handle strings, ints, uints, bools, enums and arrays. Best of all it's only a page of code!  The code you are about to see was designed using Ad Hoc tests.  The '_verbose' category is a hint to dump the object's fields and properties.  You can find more information about point and click testing here.