This page outlines what has changed in recent versions of dotPeek. Highlights
include a metadata viewer, an assembly
dependency diagram, improvements to the IL viewer,
and new ways of browsing assemblies in NuGet packages.
dotPeek 2016.3 helps you explore assembly metadata and dig through all items (tables, blobs, strings, etc.) inside it.
Under the Metadata node, you can explore values of blob items, PE file headers, usages of metadata table items.
Same as elsewhere in the assembly tree, you can
double-click metadata items to decompile and display the corresponding code.
Assembly dependency diagram
dotPeek 2016.2 can display the assembly dependency diagram, which extends the family of
dependency analysis tools
available in dotPeek and ReSharper.
You can invoke the diagram on selected assemblies in the Assembly Explorer
and explore connections that are established between the assemblies by virtue of their references.
Improved IL code viewer
dotPeek 2016.2 improves its IL Viewer in order to display code in a more readable manner:
Types, members, type parameters, and local variables, method parameters, labels, commented metadata tokens are now automatically highlighted;
Loops can now be distinguished with indents and comments.
Browsing NuGet packages
For a long time, opening .nupkg files from disk was the only way to
load assemblies from NuGet packages.
In version 2016.1, there are now two more ways: you can find and load NuGet
packages (and their dependencies if necessary) from any online package source, or load
packages listed in a packages.config file in your Visual Studio project.
Highlighting of symbol usages
dotPeek learns to automatically highlight usages of the symbol under the caret.
Among other benefits, it is much harder now for obfuscated identifiers to get lost as easily
in decompiled code.