@HansPassant "That is not a VS feature" - Look at the link in my post. I do debug of 3rd-party code a lot, most of the time to find out what they are doing wrong or see how they work to fix our code. Having the source code available means you're no longer blocked by poor or missing documentation. Valid with the. Visual Studio generates a symbol file for the assembly and then embeds the source into the symbol file. how did you get the FileGenerator plugin installed in visual studio 2013 ? See how data flows through a library or component, and watch locals change as you debug. Instead of making sure that at least basic protection is finally available, you are now making it even easier for crackers and other criminals to rob developers of their livelihood. The decompilation result is added to a temporary sub-workspace. Get results as you type and find what you're looking for easily. Decompilation of C# code made easy with Visual Studio The wikiHow Tech Team also followed the article's instructions and verified that they work. If the debugger breaks in your decompiled non-user code, for example, the No Source window appears. If, Disassembles only public types and members. This is great, but puhleeaaaaase make it so that F12 on a .NET Standard library member will forward to an actual implementation and not the useless reference assemblies. The decompilation result is added to a temporary sub-workspace. For a detailed guide to loading a file into Ildasm.exe and interpreting the output, see the Ildasm.exe Tutorial, located in the Samples folder that ships with the Windows SDK. Expand the program name next to the bracket icons. Let's be honest, there is no reason to remember how to decompile stuff with the various tools available. The sharing of source code is one thing and Im all for it. Find dependencies, diff assemblies, and understand how code works. I think the problem might be the fact that version 7 is in beta. You can enable this feature from the Tools > Options > Environment > Documents > Show Miscellaneous files in Solution Explorer checkbox. In a later step, you can extract the embedded source code. MSI to EXE Converter . What should I follow, if two altimeters show different altitudes? Open in ILSpy via the context menu of the References node in a project: Open Output in ILSpy via the context menu on the project node: Changelog 7.2.1 - Apr 4th, 2022 Bug fix release version 7.2.1 7.2 - Feb 28th, 2022 Detailed release notes for version 7.2 Requires Java (11+) to be installed system-wide. To disable Just My Code, navigate to Tools > Options (or Debug > Options) > Debugging > General, and then deselect Enable Just My Code. To do this, go to the Modules window and from the context menu of a .NET assembly, and then select the Decompile source code command. Our engineering team is working to integrate ILSpy technology into valuable debugging scenarios. This knowledge lets you build better applications and provides insight into undocumented APIs.. Obfuscators are a popular option for folks seeking an additional layer of protection. Debugging code that was decompiled from an assembly that was built using compiler optimizations may encounter the following issues: Breakpoints not always binding to the matching sourcing location, Stepping may not always step to the correction, Async/await and yield state-machines may not be fully resolved, Local variables may not have accurate names, Some variables may not be able to be evaluated in the IL Stacks is not empty.