-
Notifications
You must be signed in to change notification settings - Fork 44
Feature: Export Decompiled Code to Disk #616
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
base: master
Are you sure you want to change the base?
Feature: Export Decompiled Code to Disk #616
Conversation
| return s.endsWith("\n") ? s : `${s}\n`; | ||
| } | ||
|
|
||
| function sanitizePathSegment(segment: string) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please have a look at WholeProjectDecompiler.SanitizeFileName, because I think you are missing some special cases, especially, your code is not checking the length of the individual segments.
| ); | ||
|
|
||
| try { | ||
| await vscode.window.withProgress( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not reuse WholeProjectDecompiler instead of reinventing it in JavaScript?
|
Moved most of the logic into the backend and am now using |
|
What's the reason for disabling the generation of a project file? It seems odd to me to create a bunch of C# source code files without a project file. |
…fix progress notification
|
Sorry, forgot to remove this. Better now? |
|
Yes, thanks a lot! @Rpinski it's your turn now 😉 |
Feature: Export Decompiled Code to Disk
This PR adds a new command,
ILSpy: Export Decompiled Code..., which exports all decompiled types from a selected (loaded) assembly to a user-specified folder while preserving namespace-based directory structure.The export runs with progress + cancellation support, writes
AssemblyInfo.cs/AssemblyInfo.ilat the root, and reports any decompilation errors at the end.The command is available from the assembly node context menu in the
ILSpy: Assemblies viewand via the command palette when assemblies are loaded.