Why use serialization / deserialization functions when we can do this directly using IsolatedStorageSettings.ApplicationSettings?

Question

On a Windows phone, we can store and retrieve everything using

   IsolatedStorageSettings.ApplicationSettings.Add("foo", bar);
   IsolatedStorageSettings.ApplicationSettings["foo"]

Then why do people use the "sharpSerializer" stuff?

Answer 1

- /. , , , . , , -. , , ​​ , JSON, XML . , , . , , , , , .

PS - , Windows Phone 7, , .

Answer 2

ApplicationSettings , .

, Dictionary<string, object>, ApplicationSettings. , , .

Answer 3

:

IsolatedStorageSettings, , , .

null , .

, .

, IsolStorage. , .

, , , - - ( ) - - . serializiaton, , / . , , . , . ( .)

Answer 4

Another important point that has not yet been mentioned was that when updating the application, sending a newer version to the market, the entire ApplicationSettings will be deleted, since it is assumed that the new application will have its own default values. Therefore, it is always useful to serialize data in IsolStorage and not embed AppSettings.