This will not end well.

This will degenerate into a "I’m a better developer because I use this tool" argument.  Even worse, it focuses on what tools you are using, rather than if you are *accomplishing the job*.

Pointless and stupid.

Derik,

I’m not suggesting that an ALT.NET developer has to use NUnit over MSUnit.  More that they were aware of nUnit and using it to do their unit testing before a suitable solution like MSUnit came out of Redmond.

Also, at the moment MSUnit is only usable if you have a Team Edition of Visual Studio.  That is changing, but for now nUnit is the only choice for many developers out there.

Why would an Alt.Net developer use NUnit of MSUnit.  They DO THE SAME thing.  Just is one is Open and the other is M.S.  Personally i like them both, have used them both…. But at the end of the day, I dont CARE which i use as long as I have TESTS……

A tool is a tool, it is all about the results the tool provides.  And in this case they both provide the same results.

1. Check (R# is an absolute must)

2. Check (How could MS hire the guy who wrote NUnit and still get MSTest so wrong?)

3. Check (I hope NAnt can hang on)

4. Check (NH == nice PI domain objects, EF not so much)

5. Check (and actually MonoRail is really a MVC implementation, subtle, but important difference)