To put it simply: I've got a database design during my mind and that i would now like to use Visual Studio 2010 to produce a WPF application. Key is by using the VS2010 tools to consider almost as much ast possible manual exercise of my hands.

  • The database engine is SQLite
  • ORM most likely through DBLINQ
  • Utilization of LINQ
  • The applying can make new, empty database instances
  • Easily maintainable (alterations in data model possible)

Questions

  • How do you start creating the database model (aesthetically) in Visual Studio 2010? If this is an xsd? Will I do that inside a separate project?
  • Next, how do i take advantage utilization of VS2010 code generation tools to develop a Data Access Layer?
  • I guess the information Access Layer is going to be added like a Databases (in another project?) and after that it is a rather generic data binding solution?

I attempted finding obvious good examples of the but it is a jungle available, the search for any option would be NOT converging to 1 obvious method.

Update

And So I made the decision to make use of ADO.Internet entity framework, DBLINQ has run out of the image. I downloaded and installed the machine.Information.SQLite ADO.Internet provider which combines with VS2010. In the VS2010 Server Explorer it's possible to create and design a brand new database but it may be completed with a stand alone tool for SQLite too. Then i produced a brand new WPF application project, as well as in the answer explorer added an ADO.Internet Entity Data Model, which instantly creates an edmx with C# code (the Data Access Layer) in the already produced database file. WAF (waf.codeplex.com) appears like smart to implement the relaxation but plain LINQ to SQL is going to do. This (click here) is another very useful question on stackoverflow.

Kay,

Please think about using ADO .Internet Framework. It's based on Versus 2010 and LINQ (quick article).

There's one factor you must understand before creating your architecture. BLL (Business Logic Layer) is really a layer of logic specific for the data usage, hence can't be produced instantly by (whatever you'll use) framework. I suppose you'd Data Access Layer in your mind - don't be concerned about this - if you are likely to use ADO .Internet and LINQ to Organizations, DAL is going to be produced for you personally instantly. LINQ to Organizations along with ADO .Internet Framework are effective tools that ought to 100% cover your requirements. Additional info about LINQ to Entities.

Don't hesitate to request for those who have any queries.