Washi
## Summary dnSpy is nice for simple quick patches in CIL, but currently lacks good UX for editing data types of locals and parameters inside a method. I would love...
### Problem Description One of the major formats used for storing symbols is PDB v7.0. Symbols are often crucial when it comes to reverse engineering executable files (especially for native...
# AsmResolver.Symbols ## Status - [x] Extend AsmResolver.PE (#320) - [ ] AsmResolver.Symbols - [ ] AsmResolver.Symbols.Pdb (#323) - [ ] AsmResolver.Symbols.PortablePdb ## Overview Many compilers generate next to executable...
### Problem Description Newer .NET file formats define extensions to the metadata model that store symbols. This includes the `#Pdb` stream, as well as a couple of extra metadata table...
## Problem Description ReadyToRun (R2R) is one of the native executable code formats that was introduced in .NET Core 3.1. It is used to store precompiled CIL code to avoid...
## Problem Description Segments in an executable file are represented using the `ISegment` interface. `ISegment`s are useful, because they can be used as basic building blocks for composing a new...
# AsmResolver.Workspaces ## Overview Currently, AsmResolver is mainly tailored for processing individual PE images. This can be problematic if images have dependenices to other images. Especially with the introduction of...
## Problem Description Next to the "normal" import lookup and address tables, PE also defines [delay-load import tables](https://docs.microsoft.com/en-us/windows/win32/debug/pe-format#delay-load-import-tables-image-only) that are very similar, but are meant for DLLs that are not...
## Problem Description The PE file format defines the Attribute Certificate Table data directory that stores certificates such as an [Authenticode](https://docs.microsoft.com/en-us/windows-hardware/drivers/install/authenticode) signature. Currently, AsmResolver does not provide models that expose...