BTW, I actually already have some hooks into VS.NET  to faciliate running tests per project on build. Unfortunately I'm not a VSIP, otherwise I'd be a lot further along with the integration, instead I have to hack my way through the poorly or complety undocumented VS.NET guts.

Great! When are you writing the NAnt task? :) [The .NET Guy]

Didn't I say to post feature requests to the project site?? Besides nobody uses NAnt anyway...

Heheh, seriously though that's a great idea. What I need to do first is finish off my command line test runner, then I can wrap that as a NAnt task.

An email was just sent to the mono-list with a link to an image which shows some progress on the Gtk# project. Good stuff™!

Update: You can actually get the sample code here.

Greetings sports fans. First I want to thank everyone who sent their good wishes. This was probably the toughest week I've ever had. I came through it stronger, but changed. Not sure how much I want to write about it, but I did want to acknowledge, as soon as I possibly could, that it meant a lot to have so much support. Just got home a few minutes ago. One step at a time.   [Scripting News]

Welcome home Dave.

If anyone is doing unit testing in .NET and is looking for an alternative to NUnit, you might want to check out my .NETUnit and MetaUnit Framework libraries. My framework takes a different approach to writing test suites, cases and methods. First of all it's completely declaritive, requiring you to do nothing but mark your fixtures and methods with attributes as opposed to the J/NUnit approach of subclassing TestCase and prefixing your methods with "test". It also follows a stricter definition of what a test case should be, which I've describe here. I don't have the rich UI for executing test suites yet, but I've supplied a command line sample. It's pretty straight forward and while I haven't worked on it recently, I do plan to pick it back up soon. Please feel free to post bugs, leave comments, and request features at the project's homepage.

CppUnit revisited [IUnknown.com]

John, I think your problem with the statelessness is really a problem with the way you're trying to break up your tests. It seems like you're trying to factor your work across methods which, while normally is good practice, is not so good when it comes to test methods. A test method should be completely self contained. It should instantiate all of it's resources and they should be freed at the end. You should not pass resources across test case boundaries. If you need various test methods to perform the same steps, but those steps should vary per test method, then the steps should be coded as private methods which are delegated to by the test method.

ASP.NET without IIS. Christian Langreiter cites a fascinating article by Ted Neward entitled Hosting ASP.NET: Running an All-Managed HTTP Server [Jon's Radio]

Well done, Ted. :) [The .NET Guy]

Well done indeed!