I try to do a rather complex query (with some lazyvalue accessing) which is rather slow. So I put that quesy into a backgroundworker...
If I press the back-button, I will "save" the current dataset, which leads to an exception in:
public BinaryReader GetReader(string path)
return new BinaryReader(_iso.OpenFile(path, FileMode.Open, FileAccess.Read));
throw new SterlingIsolatedStorageException(ex);
There was an issue accessing isolated storage: Operation not permitted on IsolatedStorageFileStream.. Check the inner exception for details.
Operation not permitted on IsolatedStorageFileStream
It seems there should be an exclusive lock if this is not permitted per design.
Otherwise you will never get a responsive UI with a non blocked UI thread. Same problem as before reported with the SaveAsync feature.
If you are saving and reading data at the same time, you will get an error...
Any idea how to solve this elegantly?