When you wish to persist state across usages of your application, Isolated Storage allows you to write to the disk and stash away key-value pairs. For state, this is usually sufficient, but if what you wish to persist is data, especially relational data, then Isolated Storage is a bit limiting. To meet this need for a more robust data storage scheme, a number of libraries have been developed that work on top of isolated storage. This posting is the first in a series that will examine these options; beginning with the Sterling Database.
The home page for the Sterling Database states that the goal of Sterling is to be non-intrusive, lightweight, flexible and portable. The list of features is extensive and there is very good documentation, though it isn’t always obvious (or it wasn’t to me) how to get your first database up and running. To begin, download Sterling from Codeplex. There are two ways to install, just the dll’s or the entire source code. If you use the source code, just include the project into your solution and put a reference in your main project to the Sterling project. Read more: Jesse Liberty
The home page for the Sterling Database states that the goal of Sterling is to be non-intrusive, lightweight, flexible and portable. The list of features is extensive and there is very good documentation, though it isn’t always obvious (or it wasn’t to me) how to get your first database up and running. To begin, download Sterling from Codeplex. There are two ways to install, just the dll’s or the entire source code. If you use the source code, just include the project into your solution and put a reference in your main project to the Sterling project. Read more: Jesse Liberty
Posts
0 comments:
Post a Comment