Getting started
Published 10 July 2013
With .NET Reflector you can decompile and debug .NET components, such as assemblies, and disassemble the source code into your chosen .NET language, enabling you to see the contents of a .NET assembly.
You can use .NET Reflector to search for bugs and performance issues that may be affecting your system, and to review areas of code that were not previously accessible. For example, you may have an application that uses a third-party component, which is returning unexpected results. With .NET Reflector, you can disassemble and debug the third-party component, helping you to determine whether the component is responsible for the results.
.NET Reflector is compatible with:
- .NET Framework versions: 1.0*, 1.1*, 2.0, 3.0, 3.5, 4.0
* .NET Reflector runs under these framework versions, but the Visual Studio add-in and .NET Reflector Pro require .NET 2.0 or later. - Microsoft Windows operating systems (32-bit and 64-bit): Windows 2000
*, Windows XP SP2 or later, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7
* .NET Reflector only; not the Visual Studio add-in or .NET Reflector Pro. - Microsoft Visual Studio versions: 2005, 2008, 2010
You should ensure that your system meets the minimum requirements for the version of Microsoft Visual Studio you want to run.
You can use .NET Reflector to:
You can use .NET Reflector Pro to:
Useful examples and links
Follow these links for more help information about .NET Reflector:
- Walkthrough of .NET Reflector on Simple Talk.
- Details on .NET Reflector add-ins (CodePlex). These can be used to add functionality.Further information on these is available on Simple Talk.
- Frequently asked questions (Simple Talk) about .NET Reflector.
- Hosting .NET Reflector (Simple Talk) in your own application.
- Using the Methodist add-in (Simple Talk) to interact with your own code.
Case studies:
