Development is increasingly dependent on 3rd party technologies – using available frameworks and libraries is a great way to get stuff done fast without re-inventing the wheel. But the problem with using code you didn’t write is that you’re dependent on the documentation, and it’s hard to debug. Documentation is often missing or incomplete, and debugging stops where your own code stops. This gets even worse with a legacy code base. .NET Reflector saves time and simplifies development by letting you see and debug into the source of all the .NET code you work with.
Look inside any .NET code Debug your application
Follow bugs through your application to see where the problem is – your own code, third-party libraries, or components used by your application.
Understand how applications work
Inherited an application with no documentation and no comments? Use .NET Reflector to understand how the code runs and avoid bugs.
Look inside APIs, SharePoint, and other third-party platforms
Third-party platforms aren't always well-documented. Use .NET Reflector to look inside their assemblies, and see how they work and which APIs you can call.
Debug and decompile inside Visual Studio (VSPro edition)
Use the Visual Studio debugger
Use your regular debugging techniques on any decompiled assemblies as if they were your own, using the Visual Studio debugger.
Debug third-party assemblies
Generate .pdb files for decompiled assemblies and save them so you only need to enable debugging once for each assembly.
Assemblies decompile seamlessly in Visual Studio so source code is always available for your libraries.
Use VS shortcuts
Use F12 to “Go To Definition”, F9 to “Set Breakpoints”, and F11 to “Step Into” any decompiled code.
.NET Reflector supports C#6 and .NET 4.6.
.NET Reflector VSPro adds the Reflector Object Browser into Visual Studio. Use the tree view to navigate through code.