TestDriven.NET by Jamie Cansdale

You can download the latest version here.

Stan Lippman posted a link to Moving Your Programs from Managed Extensions for C++ to C++/CLI.  A while back I was working on a MC++ language provider for Reflector.  Unfortuantely the lack of support for jagged arrays made a lot of decompiles impossible and not having automatic boxing made others a pain.  I'm looking forward to picking up the project again with C++/CLI.

blar

I'm keeping my MSBuild Bloggers and Resources up to date with the following entry.  Let me know if I've missed anything.

Junfeng Zhang has made a number of posts recently about changes in assembly probing for .NET 2.0.  Since I deal with this stuff a lot, I thought I'd better note it here to remind myself.

I did a double take on this one. A managed debugger, written in (C#) managed code!

Nat says:

I think whenever we need to use this attribute, we should make sure that we make it internally visible to a strongly named assembly. Otherwise, this is just another crack in a pot. If we want to use it with Unit Tests, I mean that Unit Tests should be strongly named. :) Otherwise, Microsoft should make it extensible so that we can make this attribute apply only if it is a debug build. What do you think, Jamie?

Read more...

I was spelunking the .NET framework 2.0 and noticed the following assembly attribute on 'Microsoft.Build.Engine'.