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

[Feature request] Opening .NET host executables #179

Closed
PercyDan54 opened this issue Mar 5, 2023 · 3 comments
Closed

[Feature request] Opening .NET host executables #179

PercyDan54 opened this issue Mar 5, 2023 · 3 comments

Comments

@PercyDan54
Copy link

Before clicking Submit new issue, try the latest build

  • What version did you use?
    v6.3.0

  • Write down all steps needed to reproduce this issue. Also attach any needed files.

Recently I've tried JetBrains dotPeek and found a feature I'd like to see in dnSpy (it's not present in ILSpy either).

When you open a .NET host executable dnSpy just shows basic PE info, as if it's a non-.NET executable. But dotPeek shows the related assembly like this

image

@ElektroKill
Copy link
Member

ElektroKill commented Mar 5, 2023

Duplicate of #16

Support for these files is a planned feature.

@ElektroKill ElektroKill marked this as a duplicate of #16 Mar 5, 2023
@ElektroKill ElektroKill added the duplicate This issue or pull request already exists label Mar 5, 2023
@PercyDan54
Copy link
Author

PercyDan54 commented Mar 5, 2023

Duplicate of #16

Support for these files is a planned feature.

I don't think this is a duplicate. The said executable is not a single file
image

@ElektroKill
Copy link
Member

ElektroKill commented Mar 5, 2023

Oh my bad, the file you are looking at is just an apphost and not a bundle. Lyrics.exe is just bootstrap exe which runs the code in Lyrics.dll. The Lyrics.exe file does nothing else but that. If you want to analyze this application just open Lyrics.dll like you would any other file. During debugging, dnSpy will locate the correct apphost to use to start the executable.

dotPeek just automatically loads the related .dll when you load the .exe. Something dnSpy does not do as a means to make the distinction of what information is actually present in a file.

@ElektroKill ElektroKill removed the duplicate This issue or pull request already exists label Mar 5, 2023
@ElektroKill ElektroKill marked this as not a duplicate of #16 Mar 5, 2023
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

No branches or pull requests

2 participants