I recently searched for IsolatedStorage features in .NET, and I'm thinking When I when I (for example) Application.LocalUserAppDataPath .
, then my application should use them for data versus.
One thing I noticed is that the application does not exist outside of a winforms app, so it seems that the isolated storage is class libraries Some special storage may be required, especially if that library is a web app and a winform app. Is this the only difference, or is there more to it?
(As a rule, so far, I have provided the app a file stream in the library when the library may need something in general, I do not like the idea of a library, which Any type of state is external to the caller's reference.)
-
Even less reliable applications (such as That can be accessed by a single click). All apps can not access the app data. Depending on the security policy applied to the application, separate storage may also be limited, but it is usually more than the app data / file system IsolatedStorage storage requirements can be controlled by the administrator.
-
You do not have to know where the separate storage data Or how to Rhit is. It is a common API to access it on all systems that you can completely ignore the underlying path which it is placed inside. As you noted, it is very useful for a library, on which the hosting app does not have any information about how to store data.
-
You can also store data in differently-accumulated data with different levels of different levels. For more information, see. This is his name, so I think I should have listed this point first
On the negative side:
- In IsolatedStorage Some remarkable you can store there limits the amount of data, for example, app preferences will be fine, but it is not suitable for documents.
Some useful links:
Comments
Post a Comment