Follow data

See how data flows through a library or component, and watch locals change as you debug.

Find bugs

Track down the exact location of bugs in your own code or third-party libraries.

Get insight

Find dependencies, diff assemblies, and understand how code works.

Work easily with any code

Languages and libraries aren't always well-documented. Legacy code isn't always well-commented. Understand how APIs, components, frameworks, and all the critical code you use really works by decompiling and seeing inside.

Having the source code available means you're no longer blocked by poor or missing documentation. You can see how code runs, avoid bugs, and develop easily with third-party technologies.

Look inside

Create better controls, WebParts, and features by seeing how they work, and how the code runs.

Fix bugs

Track down the source of errors in your own code or the SharePoint libraries.

Get insight

Find out what methods to call and how they work, without relying on documentation.

.NET Reflector add-ins

NET Reflector has a comprehensive add-in model, with an API that lets you extend the tool to suit your exact needs.

The API also lets other tools take advantage of .NET Reflector's unparalleled decompilation and disassembly abilities to complement their own functionality. The best thing is, building your own add-in is painless.

Below are some great add-ins and tools which we recommend you try out, and there are more you can download.

We have links to some great tutorials to get you started

Our favorite add-ins

.NET Obfuscation Checker

In addition to the add-ins below, Redgate has come up with the .NET Obfuscation Checker, a tool designed to work with .NET Reflector.

Obfuscation Checker scans a directory and inspects the assemblies and .exe files inside. It shows you which DLLs and executables are there, the references for each, and information about their obfuscation state and security level.

Obfuscation Checker uses .NET Reflector to decompile the assemblies, so you can quickly see the code in a .dll or .exe file. This lets you see what's obfuscated, and what isn't. For example, you can see how readable type names are and how easy it is to understand control flow.