Open lbmaian opened 1 year ago
Do you need any of those? We picked what we considered "most common", and intentionally did not go for everything.
I just want to have the same settings I have in the GUI, and there's two ways to accomplish that: either add options for all the decompiler settings, or an option to load the same settings that the GUI uses (ILSpy.xml)
"Just because" is not a justification. I specifically asked which ones you think are missing.
For my use case, "Always qualify member references" and "Always show enum member values"
Via #2869 ilspycmd could now use settings classes.
Thanks, but I don't see any command line changes?
I'm not sure what ILSpyX even is - can't find any documentation concerning it.
I said could, not is. ILSpyX is a shared library of classes that used to be in ILSpy (now split out for reuse in other Frontends)
And, yes https://github.com/icsharpcode/ILSpy/blob/master/ICSharpCode.ILSpyX/PackageReadme.md is very thin. But we don't expect more than a handful of consumers.
Thanks for the clarification.
Is your feature request related to a problem? Please describe. The CLI does not have options corresponding to all the decompiler settings available in the GUI
Instead, it only supports the following:
--languageversion
)--no-dead-code
)--no-dead-stores
)--nested-directories
) in 8.0+Describe the solution you'd like The CLI should either or both:
%APPDATA%\ICSharpCode\ILSpy.xml
This should apply to both
ilspycmd
and the PowerShell equivalent