Reflector Desktop: When you open the dialog to read an assembly ( File > Open Assembly… menu choice or Ctrl+O) you can use the standard. Reflector is best treated as a translation aid here than a one-stop solution.ĭecompile Multiple Assemblies at one time
It’s worth noting also that Reflector hasn’t really been designed for this use case and it isn’t heavily supported, so you won’t necessarily get perfect converted code that compiles and runs without a hitch. The add-in is also available to download from the bottom of this article.)
assembly.XML) this process does not reintegrate the doc-comments back into the code there is, however, a Reflector add-in available-Denis Bauer’s File Disassembler-that does! ( Editor’s note: this is an archive link. Note that if you have the associated documentation file (e.g. Select the assembly in the assembly browser then export the source for the assembly by menu ( File > Export Assembly Source Code), context menu ( menu > Export Source Code), or keyboard ( Ctrl+S) to write out all the source files of the assembly into a new file tree.
Reflector Desktop: Have you ever had a legacy project that you wanted to convert from Visual Basic to C#? If you read the Select disassembly language feature you already know how to begin this process: set your target language in the language dropdown then load the compiled assembly (or executable) in Reflector. Note that unlike the Reflector Desktop you are limited to either C# or Visual Basic. Select the library of interest then select the target language in the Decompilation Language dropdown. There is just one pathway to decompile to a different language: choose the Generate PDBs… menu choice. NET Reflector object browser or in the VS solution explorer, it will still decompile into the same language as your current project. If you choose the Enable Debugging context menu choice in the. You can also explicitly decompile an assembly first before you ask to display the source.
With this dynamic decompilation, however, Reflector always decompiles into C# regardless of the language of your project (supporting other languages from dynamic decompilation is on Red Gate’s “to do” list but not a priority because the overwhelming majority of current users work in C#). The first time you attempt to access source for a given assembly, Reflector decompiles it then displays it.
VS Extension: Within Visual Studio you have several ways to decompile and view foreign source-see the View code without source feature above.
If you already have the source window open when you change the language, Reflector will immediately update it to the new language. You can change this dropdown setting before or after you view source code of an assembly. There are also add-ins available to supplement this list. Reflector Desktop: Reflector’s toolbar has a language dropdown that lets you select IL ( intermediate language), C#, Visual Basic, MC++, or F#. The final part is a one-page companion wallchart that summarizes every feature in parts 2 through 4 and illustrates the key points of navigation in Reflector. Part 4 rounds out the review of features explaining how to exercise the code in front of you or even any arbitrary code on the fly, as well as comparing and managing assemblies. Part 3 goes further into analyzing and exploring assemblies, showing you how to “slice and dice” to get to what you need. viewing, filtering, navigating, and debugging. Part 2 covers the “meat and potatoes”, i.e. NET Reflector, both natively and with enhancements provided by add-ins developed by the active Reflector community. This article begins a comprehensive exploration of the key features of. NET Reflector, installing it, and getting started with both the Reflector Desktop and the Visual Studio plugin.
Part 1 of this series guided you through selecting an edition of. Decompile Multiple Assemblies at one time.NET Reflector Through the Looking Glass: The Pudding - Simple Talk