ILSpyCmd: Add the ability to generate a default decompiler settings file #3607
Description
Is your feature request related to a problem? Please describe.
The new ILSpyCmd (I am testing using 10.0.0.8079 preview) added a useful argument called --ilspy-settingsfile <path> (and another one to specify the settings one by one) which is very helpful, but I have a concern about knowing what a default settings file would look like. If I were to use this feature, I would at least need a way for ILSpy to generate me a default settings file so I can modify it later since I cannot know the format in advance.
Describe the solution you'd like
A new command line argument that generates a default settings file. I can then modify this file and use the aforementioned argument more easily. This would of course generate a file that is only guaranteed to work for this particular version of ILSpy, but so does the one that loads the file.
Additional context
I feel this is especially important because the format may change with each version. It's possible settings gets added, removed or renamed and I would like to have a way to get started on a default settings file so I can change what I want. As far as I can tell, this is only possible to do by using the nuget package version of ILSpy, create a new decompiler settings object and serialising that. That's...inconvenient. I don't count the main UI version of ILSpy because it's Windows only while I use Linux and as far as I can tell, doing what I just said is the only way to get a default settings file.