I am just starting to actively participate in the development of Silverlight, and I have a certain precedent when I need to store a couple of collections of objects or strings for certain user “sessions”. I want this to be user-specific and available throughout the Silverlight application.
My first thought was to add static properties to App.xaml.
When a user logs in, I get lists of objects that this user has access to from an API call, and then saving them in the static properties of App.xaml.
Then I can access these properties on all xaml pages.
My question is, is this a specific user? Is this the best practice? Should I use isolated storage in this case? What are the limitations of isolated storage? Isolated storage, by its nature, depends on the user, right?
thank
source
share