WindowSettings.SaveWindowState ConfigurationErrorsException

[xmedeko]

We have rare error logs from our users, that saving of the window state crashes the whole application.

ConfigurationErrorsException: Failed to save settings: It is an error to use a section registered as allowExeDefinition='MachineToRoamingUser' beyond the roaming user config, in the local user config. 
...
at System.Configuration.LocalFileSettingsProvider.SetPropertyValues(SettingsContext context, SettingsPropertyValueCollection values)
at System.Configuration.SettingsBase.SaveCore()
at System.Configuration.SettingsBase.Save() at System.Configuration.ApplicationSettingsBase.Save()
at MahApps.Metro.Controls.WindowSettings.SaveWindowState() at MahApps.Metro.

We do not have defined any MahApps section in our App.config. The section MahApps.Metro.Controls... is added at runtime. It has allowExeDefinition="MachineToLocalUser" on my computer and I guess on most other users has the same. I guess some users must have configured their system to use MachineToRoamingUser by default. Or may it be caused by some changes in the system and upgrade of the settings?

Can you explicitly set AllowExeDefinition="MachineToLocalUser" in the code? Or may the Save() method be enclosed in try catch?
Thanks

• MahApps.Metro 1.5.0
• .NET 4.5.2 or higher
• OS Vista or higher
  I'm sorry do not know exact OS and .NET version.

[punker76]

@xmedeko The WindowSettings is marked as obsolete in 1.6.0 and will not be used anymore. It's now all at the WindowsSettingBehaviour. The Save method is enclosed in a try catch.

MahApps.Metro/src/MahApps.Metro/MahApps.Metro.Shared/Behaviours/WindowsSettingBehaviour.cs

Lines 171 to 178 in 1e9fabf

	try
	{
	settings.Save();
	}
	catch (Exception e)
	{
	Trace.TraceError($"{this}: The settings could not be saved! {e}");
	}