You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current implementation of the console project can be called hacky at best. Compared to the dnSpy UI it does not use MEF and instead just explicitly loads the decompiler dll and instantiates the correct decompiler object with manually created dependency objects. The debugger relies heavily on MEF since it is designed around it. It is also heavily designed around the GUI with many of its APIs. Adding debugging support to the console would be extremely laborious as the console application would need to be rewritten to use MEF just like the GUI to allow better integration of all the components. After that is done the debugger would probably need to be adjusted to also be usable in a CUI environment.
I'm interested in why you'd like to use a console debugger rather than the GUI. Would be great if you could provide some thoughts on this :p
As a final note, I don't see myself working on this in the foreseeable future as it is not that high of a priority issue and it is quite complex to implement, that is unless this turns out to be a popular feature request. Sorry!
Problem Description
Set breakpoint and debug with dnSpy.Console.exe
Proposal
A console debugger like gdb!
Alternatives
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: