Somebody in the comments of that article mentioned Heckle for Ruby ( http://ruby.sadi.st/Heckle.html ). Is there something similar for .NET?

I don't get it. Why should one want the lower layers of the application to create the instances? IMO this makes testing with mocking frameworks more difficult, because you can't inject a already initialised mockObject. Instead you tell the class under test to create a new instance of a mocked class you which have to be coded first. Does this approach take away the chance of using a mocking framework like NMock or Rhino.Mocks?

Really usefull. I'll try to improve my "code-nose" with this.

say that again frogsbrain! I, as a .net guy, found that article very interesting and even funny. I wonder where else XP and Agile method are enforced that strict... The fact that those Java-guys have these tools way befor they are ported shows me once again that maybe I should look over the .net rim more often. And imo so do you cdjaco.

Nice article, I wasn't aware of this but like those fluent interfaces and the way the code looks like when they are used.

to bad that there is no source code available...

kränk. really. I'll have to read it again...

I'll wait until the next stable release.

Nice introduction to userdefined FxCop rules. Good links in the Article.

Nice comments about OO_Design prinicples :-)

Wow, you never stop learning cool features of this language.

thanks chrismo. But still only 5 kicks. I was astonished as well...

Ankh is the way to go http://ankhsvn.tigris.org/ . I almost lmao when I read the comments of the guys at Ayende, because they seem not to use Ankh because of "the icons" and "the way it integrates" (wtf?). Ankh does a good job and saves you 50,-

C'mon Microsoft what's the point? Be proud that somebody is using your platform and is creating testdriven quality software with your product.

In the last part of this article the author encourages the use of NUnit or Nant for unit tests. IMO the good feeling about the green dots certainly disapears quite quickly when you have to switch between let's say NUnitGUI and VisualStudio. An integrated solution for the testing within the IDE is needed. I use TestDriven.Net (http://www.testdriven.net/). There is also a free (as in free beer) version of the UnitRun from ReSharper (http://www.jetbrains.com/unitrun/).

He lists some nice links with example questions in his article.