This project is read-only.


IsolatedStorageException in Save() EndStoring AppSettingsStorageMechanism


There is some issue with Save method in IsolatedStorageSettings.ApplicationSettings.Save();

Stack trace:
5 System.IO.IsolatedStorage.IsolatedStorageFileStream..ctor 908
6 System.IO.IsolatedStorage.IsolatedStorageFileStream..ctor 84
7 System.IO.IsolatedStorage.IsolatedStorageFileStream..ctor 120
8 System.IO.IsolatedStorage.IsolatedStorageFile.OpenFile 84
9 System.IO.IsolatedStorage.IsolatedStorageSettings.Save 152
10 Caliburn.Micro.AppSettingsStorageMechanism.EndStoring 196
11 Caliburn.Micro.StorageCoordinator._Save_b__11 188
12 Caliburn.Micro.ExtensionMethods.Apply 272
13 Caliburn.Micro.StorageCoordinator.Save 1192
14 Caliburn.Micro.StorageCoordinator.OnDeactivated 180
Closed Jan 10, 2013 at 9:18 PM by tibel
I'm sorry, but I don't think that we can do anything about this.


tibel wrote Jan 2, 2013 at 10:58 AM

May you add some sample project that shows the issue, please.

tibel wrote Jan 7, 2013 at 9:04 AM

You most probably hit the size quota for the IsolatedStorageFile that stores the ApplicationSettings:

Other possibility is this:
On Silverlight for Windows Phone, IsolatedStorageSettings is not thread safe and throws an IsolatedStorageException when Save() is called.

How much data are you trying to store?

tibel wrote Jan 7, 2013 at 6:58 PM

Have you any futher details on the issue (e.g. exception message)?
Otherwise I have to close this issue as there is nothing we can do.

Found out that quotas are not enforced on WP7, so that cannot be an issue here.

nuwanda wrote Jul 30, 2014 at 12:09 PM


Shouldn't StorageCoordinator be fail proof? I am experiencing the very same issue (in production, not knowing anything more than exception data from the Windows Store).

I would expect that if anything goes wrong while persisting, it won't affect the application overall state.