What′s New in dotPeek

dotPeek 2022.3 comes with support for:

• static abstract and static virtual members in interfaces.
• generic attributes.
• user-defined checked operators.
• unsigned right shift operator.

There is now an option to view decompiled high-level and low-level C# code in the IL Viewer tool window. The decompiled code is still synced to the source code in the code editor.

• The way ReadyToRun (R2R) and NGen assemblies are presented in the Assembly Explorer has been improved. A small processor symbol icon and ngen or R2R labels are now displayed next to each assembly's name.
• The Metadata tree has the ReadyToRun header.
• The Properties window has the ReadyToRun section.

We introduced the ability to show files in a single Preview tab, as you are used to in Visual Studio. It helps when you are looking for something specific and don't want to keep these files open as separate tabs.

If you want to keep the file in a separate tab, click the Keep open icon on the Preview tab. To disable the Preview tab, go to Tools | Options | Tabs and select Allow new files to be opened in the preview tab.

We moved the Quick Find feature from a separate tool window to the text editor tab. Now, when you call Quick Find (Ctrl+F) for a file, the Quick Find pane appears inside the text editor tab for the file.

We also added the F3 and Shift+F3 shortcuts, which allow you to quickly navigate to the next or previous occurrence when you are looking for something using the Quick Find pane.

dotPeek now shows XML doc comments for platform assemblies, including assemblies whose names differ from the names of the XML documentation files, for example, System.Private.CoreLib. The path to the XML documentation is now displayed in the decompiled file’s header.

dotPeek provides initial support for record and record struct types. Support for the with expression for records, record structs, and structs is also available.

As for other C# features included in this release, the decompiler now supports asynchronous dispose (await using).

We’re continuing to improve our support for reading and decompiling single-file apps:

• You can see the content of bundled .json files – for example, the .runtimeconfig.json file.
• You can view a list of all embedded files along with some technical information about the single-file app (header format version and ID) by clicking on the root node in the Assembly Explorer.
• You can extract all the files to a folder (using the Extract Bundle Content to Folder action from the context menu) or one particular file from the bundle as an external file (using the Extract to File action in the context menu).

Now dotPeek can decompile single-file apps. It also lets you browse through bundled assemblies inside a single-file app just like you are used to doing. It supports single-file formats for the .NET Core 3.1, .NET 5, and the upcoming .NET 6 SDKs.

When working with several tabs at once, you can now pin them. Additionally, the color of a tab indicates the type of code you will see – green represents a metadata view and brown stands for sources from symbol files. The options to pin tabs and to color code them can be disabled in Tools | Options | Environment | Tabs.

We’ve updated the formatter for decompiled code with a set of options to control how the code is presented. You can now set indent style and size, select whether the open brace should be placed on a new line, and if you’d prefer to use expression-bodied members. You can find them in Tools | Options | Decompiler | Code style and formatting.