NGWS SDK Documentation  

This is preliminary documentation and subject to change.
To comment on this topic, please send us email at ngwssdk@microsoft.com. Thanks!

Handling out-of-space conditions

Isolated storage can only be used within the limitations established by administrators and policy, and within the constraints of available backing storage. When an attempt to write data exceeds any of these limitations (after all available space has been reclaimed) an exception is raised and the operation fails.

Generally there will be no way for applications to recover when this happens. For guaranteed retention stores this is identical to the classic full-disk problem; for other uses isolated storage is always subject to expiration so the application needs to be able to continue even if all storage is lost.

To aid applications handling these potential space problems, some simple aids are provided. The current and maximum size of a store can be determined with the get-only properties IsolatedStorage.CurrentSize and IsolatedStorage.MaximumSize. The maximum is not a guarantee, but simply a measure of the space available at the time: concurrent use of isolated storage means it is always possible that space may be consumed between checking maximum size and actually attempting to use it. However, the maximum size can reasonably be used as an upper limit on available storage.