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.

Debug third-party code fast

Using third-party technologies is a great way to get stuff done fast without re-inventing the wheel. But it's hard to debug libraries, components, and frameworks you didn't write.

.NET Reflector saves time and simplifies development by letting you see and debug into the source of all the .NET code you work with.

Follow bugs through your own code, third-party components, and any compiled .NET code you work with. You can see third-party code in Visual Studio, and debug into it just like your own.

Better docs

Replace poor or missing documentation by seeing how the code works in context.

Discover methods

Find unexposed and undocumented functionality and get more out of the APIs and technologies you're using.

Learn tech

Drill into how .NET languages and frameworks are implemented, and learn how to use them.

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.

Simplify SharePoint development

SharePoint APIs and libraries aren't always well-documented, or exposed in the way you need. But that doesn't have to be a problem.

With .NET Reflector you can look inside the SharePoint assemblies and understand exactly how they work.