c# - Persisting user preferences in Silverlight -
I am working on a Silverlight client and related ASP.NET web services (not WCF), and give me some features There is a need to implement that has user preferences such as "Favorite Items" system and whether they are word-wrapping or not, to experience a pleasant (infamous) user, I want to keep these settings throughout the session. A brief investigation reveals that there are two main possibilities.
- Silverlight isolated storage
- ASP.NET-accessible database
I know this option 2 is probably the best option because it Ensures that if a user disables different storage for Silverlight, then their preferences still persist, but I would like to avoid the burden of maintaining the database at this time, and I like it That when server connectivity is unavailable Children are also priorities for the loading and editing. However, for the logical debate, I openly argue why it may be the priority to take this hit later.
Anything that I see is a suggestion on the best way to apply the circumstances under the circumstances. For example, if different storage is used, should I use an XML format, or some other file layout to continue the settings; If the database approach is used, then do I have to prepare a testing table or an underlying mechanism to support it in ASP.NET, and how do I serve the priorities for clients?
:
Which solution is a better solution for user-priority persistence? How can the setting be maintained in that solution, and how can customers access and update it?
Pre-research
Note that I have done a little research on this matter and have found that the following links, which seem to be the lawyer for the solution based on the article you have read.
update
It has come to the notice that Microsoft has installed the Silverlight The setting has been firmly established as an underlying component (I have not missed it until I apply it to an alternate option). There is more information on this.
I firmly support Microsoft's client-side settings Also, it is not necessary to maintain this user preferences. The best way to do it and I would like more advice on canvas and suggestion on this.
After checking for something else and after implementing its own XML file-based settings , I user-specific, specially searched for a key / value collection class and object to store application settings.
It all seems obvious now, in the long run, a mechanism for backup and restore settings to use a server database will be a good increase in this client-side settings.
Comments
Post a Comment