jdh, that would leave all of us C++, Java, and C# devs out in the cold. :-)

When I submitted this story, it wasn't a duplicate. Unfortunately, some other story made it to the front page first, so apologies for the dupe.

Duplicate, IIRC.

"Its about life time management in the CLR!!!"

Thanks for the infoooooooo!!!!!111111onehundredeleven

Keep up the great work, Wes. Looking forward to your tool.

Article refers to the original blog post by NStatic creater Wesner Moise. The original has been kicked: http://dotnetkicks.com/products/Can_a_NET_code_analysis_tool_approach_human_intelligence

Go Wes!

Wesner Moise, the developer of NStatic, has been blogging about this NStatic tool for well over a year now and has had the dev community give him feedback on UI, how things should work, as well as giving some great insight into UI design, AI, and static analysis. I've been looking forward to his tool for a long time now, can't wait to test it out.

Wes says the day he plans on releasing it, he'll release it with the headline "2000+ bugs found in the .NET framework" (don't recall the exact number) that his tool found when running on shared source Rotor framework. So, keep an eye out for that headline. :-)

Good article, but doesn't get into any of the problems when doing unit tests. For example, unit testing your UI is a pain in the ass. Unit testing your data access layer that talk to the database is also a huge pain.

Both problems are solvable (MVP design pattern for UIs, frameworks built atop NUnit like Roy Osherove's XTUnit), but they are not addressed in the article. It leaves the reader with a rainbow faery world view of unit testing. The reality is that unit tests are very difficult to write for large sections of code and require much more than the simple examples put forth in the article.

Does this inject a particular version of the CLR into every explorer process? If so, doing this is highly discouraged because it will cause major problems with the shell and any app that uses the shell (such as OpenfileDialog, etc.).

That list is fairly incomplete. A more exhaustive list is available at www.dotnetpowered.com/languages.aspx

Cool, I wasn't aware of this API. Thanks for the info!

And kudos to the DotNetKicks team, this site rocks! Keep up the good work.

Is that right? Ah, thanks for the info. I'm surprised, frankly, after having read his thorough trashing of the new UI framework several months back.

Kind of misleading though, since, as I understand it, Miguel is not committed to supporting WPF, which I think is really what the devs were trying to asking him.

Sweet! Looks great.