Searching and filtering using lowerCamelHumps is supported for these scenarios. In addition to the set of features that streamline debugging decompiled code, dotPeek 1.2 adds quick search and node filtering in various trees, most notably Assembly Explorer. To address cases when it’s not clear whether PDB files were generated properly, dotPeek has a dedicated tool window that shows current status and results of PDB generation. In order to do that, simply select an assembly in dotPeek’s Assembly Explorer, right-click it and choose Generate PDB.ĭotPeek can export to project and generate PDB files in the background, meaning that you can explore assemblies during PDB generation or assembly export. In case that the Visual Studio cache already contains PDB files for certain assemblies but you would like to replace them with PDB files generated by dotPeek, use the option to generate PDB files manually.

To learn more on how to set up dotPeek as a symbol server and use it for debugging in Visual Studio, please refer to this guide. dotPeek provides several options to choose exactly which assemblies you want it to generate symbol files for. This can be most useful when debugging a project that references an assembly from an external class library.ĭotPeek listens for requests from Visual Studio debugger, generates PDB files and source files for the requested assemblies on demand, and returns them back to the debugger. Starting from version 1.2 dotPeek learns to perform as a symbol server and supply Visual Studio debugger with the information required to debug assembly code. Today we’re ready to launch the dotPeek 1.2 Early Access Program that introduces a substantial set of new features. NET decompiler, received its latest update, but that doesn’t mean we put it aside. It has been a while since dotPeek, our free.

Jet brains dotpeek