When and Why To Use Isolated Storage (or NOT!)...

When implementing low or least privilege type applications and permissions, it is a good choice. Refers to an information or data storage mechanism providing isolation and safety, adding levels of security and peace of mind. This is done effectively  by defining standardized ways of associating code with saved data. It is private, user, domain and assembly level(s).  Only the person who created it can access it (restricted). Isolation can also be done by application domain, for added security and improved performance. There are THREE classes of isolated storage: IsolatedStorageFile, IsolatedStorageFileStream, IsolatedStorageException. Knowledge on how to create and access these stores, writing and using these files, streams and storage (standard text file) are all essential skills.

This standardization functionality and results also provide other benefits as well. (i) File-configurations for/of storage space, (ii) setting of security policies, and (iii) deleting unused data.

With separate/detached or isolated storage, programming code does not need unique paths to specify safe locations in the file system any longer. Data is protected from other applications which only has isolated storage. No more hard-coded locale information indicators are required. (this provides better and more security).

Now through this isolation type processes, partially trusted applications can also store data, in so much it is then rather controlled by the computer's security policy. (deeper, wider and more security consistency and less risk of breaches or attacks, hacking or such related threats).

It is particularly best-fit for Web applications and downloaded components for which additional caution would be required.  Code running from the local computer, a local network, or the Internet, is granted the right to use isolated storage. Ensure familiarity with isolation stores, creation and use.

Isolated storage is useful in many situations, like download control, persistent web application storage, shared component, server storage, roaming. It should not be utilized and called on for high-value secrets, unencrypted keys or passwords, as it is unprotected from highly trusted code, from unmanaged code, or from trusted users of the computer. Code should not be stored here, or used for configuration or deployment settings (administrative rights and permissions) Some database uses and applications, are also permissible, for few # of users, flexibility and viable alternative.

Key Exam Points

1. Review chapters on Input/output and fundamentals, including reading and writing files and streams, file management and changes, flexible data storage, data compression or isolated storage.

2. For the exam,  study practical and hands-on examples, illustrative exercises, real-life scenarios and applications,  for isolated storage usages, creation and method, that help you to gain a better understanding of this topic

3. Take the practice test, Q&A Multiple Choice and Application Type questions, skills-demonstration

Related Terms

Deflate, GZip

This article is based on the 2nd edition of the Microsoft .Net Framework Application Training Kit with the purpose to help 70-536 Exam takers to succeed. I constantly look for ways to improve the content.   Please leave a comment about this article or drop me a message if you would like to see changes for this site.