MSDN Status:
- None No isolated storage is used.
- User Isolated storage with user authentication.
- Domain Sandbox storage is bound to the application domain identifier.
- Assembly Isolated storage with assembly identification.
- Roaming Isolated storage can be placed in a folder in the file system that can be moved (if user roaming data is included in the base operating system).
- Machine Isolated storage attached to a machine.
- Application Isolated storage associated with the application.
I have some problems understanding what these levels mean in detail. This is what I can do (developing a Windows Form application):
- User Storage location will change when another Windows user starts the application
- Domain What is a domain identifier and for which use case will this parameter matter?
- Assembly . How exactly does the assembly identify? It looks like the storage location is changing with the assembly version changing.
- Roaming This will probably tell .NET to use the roaming data folder for the current user (if available). However, some additional flags are probably required, as he somehow needs to know how to determine the application folder.
- The car . Will it be used to share data between applications storing it in a “shared” space with isolated storage?
- Application . How is this different from Assembly?
What would be the right combination for storing data related to a Windows Forms application, but regardless of the build / file version, for storing data between updates?
A general description of all the flags will be pleasant.
source share