On Her Majesty’s Secret Source Code: .NET Reflector 7 Early Access Builds Now Available

Dodgy Bond references aside, I’m extremely happy to be able to tell you that we’ve just released our first .NET Reflector 7 Early Access build. We’re going to make these available over the coming weeks via the main .NET Reflector download page at:


Please have a play and tell us what you think in the forum we’ve set up. Also, please let us know if you run into any problems in the same place.

The new version so far comes with numerous decompilation improvements including (after 5 years!) support for iterator blocks – i.e., the yield statement first seen in .NET 2.0. We’ve also done a lot of work to solidify the support for .NET 4.0. Clive’s written about the work he’s done to support iterator blocks in much more detail here, along with the odd problem he’s encountered when dealing with compiler generated code: http://www.simple-talk.com/community/blogs/clivet/96199.aspx.

On the UI front we’ve started what will ultimately be a rewrite of the entire front-end, albeit broken into stages over two or three major releases. The most obvious addition at the moment is tabbed browsing, which you can see in Figure 1.


Figure 1. .NET Reflector’s new tabbed decompilation feature. Use CTRL+Click on any item in the assembly browser tree, or any link in the source code view, to open it in a new tab.

This isn’t by any means finished. I’ll be tying up loose ends for the next few weeks, with a major focus on performance and resource usage. .NET Reflector has historically been a largely single-threaded application which has been fine up until now but, as you might expect, the addition of browser-style tabbing has pushed this approach somewhat beyond its limit. You can see this if you refresh the assemblies list by hitting F5. This shows up another problem: we really need to make Reflector remember everything you had open before you refreshed the list, rather than just the last item you viewed – I discovered that it’s always done the latter, but it used to hide all panes apart from the treeview after a Refresh, including the decompiler/disassembler window.

Ultimately I’ve got plans to add the whole VS/Chrome/Firefox style ability to drag a tab into the middle of nowhere to spawn a new window, but I need to be mindful of the add-ins, amongst other things, so it’s possible that might slip to a 7.5 or 8.0 release.

You’ll also notice that .NET Reflector 7 now needs .NET 3.5 or later to run. We made this jump because we wanted to offer ourselves a much better chance of adding some really cool functionality to support newer technologies, such as Silverlight and Windows Phone 7.

We’ve also taken the opportunity to start using WPF for UI development, which has frankly been a godsend. The learning curve is practically vertical but, I kid you not, it’s just a far better world. Really. Stop using WinForms. Now. Why are you still using it? I had to go back and work on an old WinForms dialog for an hour or two yesterday and it really made me wince. The point is we’ll be able to move the UI in some exciting new directions that will make Reflector easier to use whilst continuing to develop its functionality without (and this is key) cluttering the interface. The 3.5 language enhancements should also enable us to be much more productive over the longer term.

I know most of you have .NET Fx 3.5 or 4.0 already but, if you do need to install a new version, I’d recommend you jump straight to 4.0 because, for one thing, it’s faster, and if you’re starting afresh there’s really no reason not to.


Despite the Fx version jump the Visual Studio add-in should still work fine in Visual Studio 2005, and obviously will continue to work in Visual Studio 2008 and 2010. If you do run into problems, again, please let us know here. As before, we continue to support every edition of Visual Studio exception the Express Editions.

Speaking of Visual Studio, we’ve also been improving the add-in. You can now open and explore decompiled code for any referenced assembly in any project in your solution. Just right-click on the reference, then click Decompile and Explore on the context menu. Reflector will pop up a progress box whilst it decompiles your assembly (Figure 2) – you can move this out of the way whilst you carry on working.


Figure 2. Decompilation progress. This isn’t modal so you can just move it out of the way and carry on working.

Once it’s done you can explore your assembly in the Reflector treeview (Figure 3), also accessible via the .NET Reflector > Explore Decompiled Assemblies main menu item. Double-click on any item to open decompiled source in the Visual Studio source code view. Use right-click and Go To Definition on the source view context menu to navigate through the code.


Figure 3. Using the .NET Reflector treeview within Visual Studio. Double-click on any item to open decompiled source in the source code view.

There are loads of other changes and fixes that have gone in, often under the hood, which I don’t have room to talk about here, and plenty more to come over the next few weeks. I’ll try to keep you abreast of new functionality and changes as they go in.

There are a couple of smaller things worth mentioning now though.

Firstly, we’ve reorganised the menus and toolbar in Reflector itself to more closely mirror what you might be used to in other applications.

Secondly, we’ve tried to make some of the functionality more discoverable. For example, you can now switch decompilation target framework version directly from the toolbar – and the default is now .NET 4.0.

I think that about covers it for the moment. As I said, please use the new version, and send us your feedback. Here’s that download URL again: http://reflector.red-gate.com/Download.aspx.

Until next time!

(Remember, you can also follow .NET Reflector’s progress and updates on Twitter.)