Not sure if this is fixed in current version (I'm using and older version, able to be built with VS2019).
I had an ILSpy.xml with a metric ton of data. Many groups, and many, many assemblies listed.
Most likely I introduced an error in the XML when last adding another metric ton of entries to the settings file directly.
Actual:
On startup, ILSpy destroyed the existing file, overwriting it with the default ILSpy.xml, without notifying me of malformed entries or even backing up the existing file.
Expected:
If ILSpy found errors while parsing the settings file on startup, notify the user of this error, but vitally do not overwrite it with the default settings file. I don't care if it's automatically backed up or asks the user for confirmation, but data loss should not be an option.
Not sure if this is fixed in current version (I'm using and older version, able to be built with VS2019).
I had an
ILSpy.xmlwith a metric ton of data. Many groups, and many, many assemblies listed.Most likely I introduced an error in the XML when last adding another metric ton of entries to the settings file directly.
Actual:
On startup, ILSpy destroyed the existing file, overwriting it with the default
ILSpy.xml, without notifying me of malformed entries or even backing up the existing file.Expected:
If ILSpy found errors while parsing the settings file on startup, notify the user of this error, but vitally do not overwrite it with the default settings file. I don't care if it's automatically backed up or asks the user for confirmation, but data loss should not be an option.