Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for loading/editing/saving .NET Core single file publish bundles. (#16) #49

Draft
wants to merge 11 commits into
base: master
Choose a base branch
from

Conversation

ElektroKill
Copy link
Member

@ElektroKill ElektroKill commented Nov 14, 2021

This PR aims to bring support for loading, editing, and saving .NET Core single file bundles.

Current implementation status:
dnSpy is able to display assembly entries of bundles and allows editing and saving said assemblies (excluding hex editor).

Roadmap:

  • Fix AssemblyResolver to work properly for assemblies inside bundles.
  • Iron out some of the remaining jump to reference bugs (e.g. namespaces).
  • Pass the embedded symbol files to dnlib to provide additional information to decompiler.
  • Add support for editing the single file bundle itself .
  • Add support for showing all the other entries a bundle can have in the tree view.
  • Add Hex editor support for the embedded assemblies.
  • Bundles can have folders inside them, these need to be replicated in the tree view.
  • Debugging support for bundles.

Some of these regular dnSpy features require the file to be present in the filesystem. An example of such a feature is the Hex editor. I'm still debating whether support for this feature should be left out or should we write the extracted bundle entries to disk in a temporary location.

fixes #16

@ElektroKill ElektroKill added this to the 6.2 milestone Nov 14, 2021
@ElektroKill
Copy link
Member Author

This feature will not make it into dnSpyEx 6.2. I severely underestimated the difficulty of properly implementing this feature. Furthermore, I kind of lost interest in implementing this feature so for now it will be placed on hold. Sorry!

@ElektroKill ElektroKill removed this from the 6.2 milestone May 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support for .NET Single file publishing.
2 participants