Today we are proud to announce the release of .NET Reflector v7.5. This release brings several enhancements to our Visual Studio integration, as well as improvements to the stability, performance, and design of Reflector itself. The new features allow developers to decompile, debug, and understand any .NET code within Visual Studio, using Visual Studio’s native debugging workflows.
Our roadmap for 7.5 was to bring you:
- A fully-featured Reflector Object Browser (ROB) inside Visual Studio
- Dynamic type-by-type decompilation in the Visual Studio editor
- An improved Visual Studio debugging experience, step straight into code without source
Our eventual goal for Reflector is to make working with any code as easy as working with your own, and 7.5 is a big step towards that. As you can see from our extensive changelog, we’ve worked hard to make our integration with Visual Studio closer to seamless, and to bring powerful dynamic decompilation right into your normal workflow.
You can read more about the work that went into .NET Reflector 7.5, but for us the highlights above and beyond the basic roadmap would have to be:
- The ability to Go To Definition (F12) on any .NET code, whether you have the source code or not
- PDB files are now automatically generated when you set a breakpoint
- PDBs can be generated in parallel, and in ways that will fit smoothly into your workflow
- Design and UX enhancements to improve the Reflector experience is Visual Studio
- Reflector is now a Visual Studio Package, rather than an add-in. We’ll be able to do much more to support developers with this deeper integration with VS.
We’d also like to say a huge thank you to all of our EAP users for all of their feedback and their time. Download a free trial of .NET Reflector 7.5 and take the new features for a spin, and leave us comments to let us know what you think!
What the .NET Reflector team have to say:
“I really like the type by type decompilation, sometimes I don’t want to have to decompile a whole assembly, I just want to look at a specific method and work out how my code is calling it. I enjoyed working alongside a truly super team that have drive and passion for what they do.”
“For me, just to see the management of assemblies in Visual Studio that much better is a highlight, even though there is a ton of room for improvement that we will see in the future. I’m also looking forward to seeing more people enjoy the VS add-in thanks to the new VS install screens.”
“It was when I was demoing the stuff internally I thought – actually this is pretty cool, I can actually use this. And since then I have. Extensively.”
“We want to make Reflector an indispensable tool for all our users, and the best way to do that is to bring the tool right into to Visual Studio. Seamless integration is what we’re talking about. Reflector 7.5 is a step closer to this goal. I love everything about what we’ve implemented so far, be it hitting F12 to navigate to definition or setting breakpoints in code without source. It goes to show how close we are to our goal!”
“Whenever we’ve demo’d the tool internally, I’ve enjoyed seeing the same scene play out:
Developer quickly and easily step into source code they didn’t have a second go, leans back <impressed face>, “That’s really cool”. Its a great feeling to see that reaction.”
“I don’t spend all that much time in Visual Studio. So, as a n00b, the way the add-in behaviour is converging on a standard development workflow – with so little faffing about – made v7.5 so much easier to get to grips with.”
Previous posts mentioning 7.5
- .NET Reflector V7.5 EAP Build 1
- .NET Reflector V7.5 EAP Build 2
- Morrissey: Byte Code Manipulation using Reflector
- .NET Reflector V7.5 EAP Build 3
- .NET reflector V7.5 EAP Build 4
- A little pre-Christmas housekeeping – early access build 5
- Early Access Build 7: A Leap Build