![]() ![]() ![]() Think of it as a Dictionary() object, but it is automatically loaded from and saved to disk without extra code. It has a PersistentDictionary object that is quite easy to use. This is a managed wrapper for the ESENT Win32 API. It provides reliable, transacted, concurrent, high-performance data storage with row-level locking, write-ahead logging and snapshot isolation. If you need an easy, free way to scale to millions of pieces of data, try out the ESENT Managed Interface project on GitHub or from NuGet.ĮSENT is an embeddable database storage engine (ISAM) which is part of Windows. There are plenty of 'how to' responses here on serialisation, which is my fault since I didn't make it clearer early on, but now I'm looking for a definite solution.Īll of the above are good answers, and generally solve the problem. Obtaining this layout from a Dictionary> is the tricky bit, and the essence of this question. It is my understanding that the goal here is to try and end up with this: Each Account is fairly simple, it's just a bunch of properties. What makes it complicated is that the value for this dict is a generic itself, which is a list of complex data structures of type Account. So it's possible to serialize a dictionary. Would I serialize the dict as the xmlroot, and then the Account type as attributes? The options I believe are thus:įlat files require a bit more effort to maintain (no built in classes like with XML), however I haven't used XML before, and SQL seems like overkill for this relatively easy task.Īre there any other avenues worth exploring? If not, which of these is the best solution?Įdit: To add a little more data to the problem, basically the only thing I'd like to store is a Dictionary that looks like this Dictionary> ![]() It'd be fairly straightforward if I used flat files, as the data doesn't really need to be secured (it'll only be stored on this PC). The application will be started and stopped fairly often, and I'd like to make it save/load the data on application start/end. I'm writing an application that takes user data and stores it locally for use later. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |