dnSpyEx / dnSpy

Unofficial revival of the well known .NET debugger and assembly editor, dnSpy
GNU General Public License v3.0
6.14k stars 412 forks source link

Drag and drop to file to editor not working fo x86 netframework version #291

Closed ewwink closed 4 months ago

ewwink commented 5 months ago

dnSpyEx version

6.5.0 rc3

Describe the Bug

I cannot drop any file to x86 editor

How To Reproduce

drag and drop exe or dll from windows explore to editor

Expected Behavior

File should be in assembly explorer like in x64 version

Actual Behavior

nothing dropped to assembly explorer

Additional Context

No response

ElektroKill commented 5 months ago

I cannot reproduce the issue you are facing. When I drag and drop a .exe file onto dnSpy-x86 from the netframework distribution of 6.5.0-rc3, it appears in the assembly explorer without issues. Make sure you are NOT running dnSpy as administrator though. Running applications as Administrator interferes with the drag-and-drop functionality (this is a known windows issue).

ewwink commented 5 months ago

you are right, Running as Administrator causing the problem, uncheck the option and it now working.

Thank you

image

ewwink commented 5 months ago

Reopening, if target app require admin right we cannot debug, can it prompt user to automatically re-launch the app as administrator?

ElektroKill commented 4 months ago

Reopening, if target app require admin right we cannot debug, can it prompt user to automatically re-launch the app as administrator?

I've added an option in the File menu to restart dnSpy as administrator. If the debugger states this is necessary, you can now use this option.

Deltafox79 commented 4 months ago

Reopening, if target app require admin right we cannot debug, can it prompt user to automatically re-launch the app as administrator?

I've added an option in the File menu to restart dnSpy as administrator. If the debugger states this is necessary, you can now use this option.

Not work on Net 8.0 Release x64/x86

Regards

ElektroKill commented 4 months ago

Fixed in the latest build!