Windows apps
Collapse the table of content
Expand the table of content
Information
The topic you requested is included in another documentation set. For convenience, it's displayed below. Choose Switch to see the topic in its original location.

IsolatedStorage::MaximumSize Property

 
obsoleteCodeEntityP:System.IO.IsolatedStorage.IsolatedStorage.Quota Note: This API is now obsolete.

Gets a value representing the maximum amount of space available for isolated storage. When overridden in a derived class, this value can take different units of measure.

This API is not CLS-compliant.

Namespace:   System.IO.IsolatedStorage
Assembly:  mscorlib (in mscorlib.dll)

public:
[CLSCompliantAttribute(false)]
[ObsoleteAttribute("IsolatedStorage.MaximumSize has been deprecated because it is not CLS Compliant.  To get the maximum size use IsolatedStorage.Quota")]
property unsigned long long MaximumSize {
	virtual unsigned long long get();
}

Property Value

Type: System::UInt64

The maximum amount of isolated storage space in bytes. Derived classes can return different units of value.

Exception Condition
InvalidOperationException

The quota has not been defined.

The default implementation of the MaximumSize property returns the value of IsolatedStoragePermission::UserQuota, which is expressed in bytes. Derived classes can express the value in other units of measure. A potential example of such an implementation is an isolated storage database.

You cannot set MaximumSize, but the quota is configured in the security policy, and can be set. Code receives a quota of space on the basis of its evidence, so the same code can receive a different quota if it is run with different evidence (for example, the same application run locally and from a share on an intranet can receive different quotas). IsolatedStorageFile::MaximumSize implements this property.

.NET Framework
Available since 1.1
Return to top
Show:
© 2017 Microsoft