By now you may well have noticed that .NET Reflector 6 and .NET Reflector Pro are out in the wild. The official launch happened today, although we actually put the software out last Thursday as part of a phased release plan to ensure that everything went smoothly today which, so far, it seems to have done.
Clive and Alex have already talked extensively about what the new version and the Pro extension do, so I’m not going to go into any detail here, but I’ve linked to their blogs at the bottom. What I want to do here is provide anyone who’s using TestDriven.NET, .NET 4.0, or Mono, with some useful information.
First off, TestDriven.NET. Jamie Cansdale has been working hard to make TestDriven.NET and .NET Reflector work well together. He tells me that the mechanism that downloads .NET Reflector automatically in the current version of TestDriven.NET (2.24.2554) won’t work properly with .NET Reflector 6, because the Visual Studio add-in won’t be installed, but that a fix will be available in TestDriven.NET 3 Beta, which will be released soon. Now as it turns out, if you desperately need it, Jamie’s already put the fix into this preview build:
I know a few of you have been wondering about support for the C# 4 and VB 10 language extensions coming in .NET 4.0. We’ve already started work on decompilation support for these, which will be available in the free version of .NET Reflector, and are hoping to have them ready around the time .NET 4.0 ships in a couple of months or so. In the meantime, .NET Reflector will work fine with .NET 4.0 assemblies, it’s just that you won’t see any of the new syntax in the decompiled code.
We’ve also now made available a Mono compatible build of .NET Reflector 5 at:
Please note that this build will only run on the Mono runtime.
That’s about it from me, but if you want to know more about .NET Reflector 6 and .NET Reflector Pro take a look at Clive’s and Alex’s blogs: