When you say "data persistence" do you mean "a database with multiple tables", or do you mean something as simple as "one or more instances of a particular .NET object"? It is often easy to store instances of .NET objects in a file, using the serialization facilities that come with .NET.
If you need more data than will fit in RAM, Frans's Firebird suggestion makes good sense. If the data is relatively trivial, rolling something based on serialization will be a lot less effort. Are you sure you should be using .NET for this? Many consumers do not have .NET framework installed, and might not appreciate the 20+MB download and 2800+ registry entries created by its installation. At 01:25 AM 12/21/2004, Scott wrote >I'm new to the .NET framework and I'm trying to write a consumer >application that requires data persistence. It should be lightweight, so >it shouldn't require a separate database installation. It should also not >require a commercial license (i.e. it should be free). Does anyone have >any suggestions? > >Thanks. > >Scott J. Merrill / Analytical Software Corp =================================== This list is hosted by DevelopMentorŪ http://www.develop.com Some .NET courses you may be interested in: Essential .NET: building applications and components with C# November 29 - December 3, in Los Angeles http://www.develop.com/courses/edotnet View archives and manage your subscription(s) at http://discuss.develop.com
