Isolated Storage

In general, whenever we store something somewhere, the two things we do remember and take care for future references

1. Proper Name

2. Specific Location

In the same manner whenever we store some file in some location, we always think of the name of file and location where file is to be stored. So when an application stores any data in a file, the file name and storage location chosen carefully to minimize the possibility of being used by other application and to avoid vulnerability.

Isolated storage is a mechanism which is used to isolate and save the data by the user and even by the assembly. Whenever we use isolated storage, our application saves data in data compartment that consists of one or more isolated storage file which contains the actual directory location. The data compartment is not a specific storage location but an abstraction. Isolated storage can be on client side as well as on the server side.

It enables partially trusted applications to store data in such a way so that it could be controlled by computer’s security policy specially used for downloaded material which is used to run very cautiously. However, by default, code running from the local computer or local network or the internet is granted the right to use the isolated storage. To access isolated storage, code must have all necessary native platform operating system rights. .NET Framework applications already have operating system rights to access isolated storage unless they perform (platform-specific) impersonation.  This access provides a convenient way for code that is run or downloaded from the web to read and write to a storage area related to a particular user.

Storage locations in Windows 8, Windows 7, Windows Server 2008, and Windows Vista:

Roaming-enabled stores = \Users\\AppData\Roaming Nonroaming stores = \Users\\AppData\Local There are three classes to perform tasks related to isolated storage in .Net framework 1.IsolatedStorageFile 2.IsolatedStorageFileStream 3.IsolatedStorageScope