StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>Continuing from the comments which brought up Entity Framework:</p> <p><strong><a href="http://msdn.microsoft.com/en-us/library/aa697427%28VS.80%29.aspx" rel="nofollow noreferrer">Entity Framework</a></strong> <a href="http://en.wikipedia.org/wiki/Entity_Data_Model" rel="nofollow noreferrer">(wikipedia also has some nicely structured information)</a></p> <ul> <li>supports both code first, model first and database first development. The difference between code first and model first is that in code first you write the entity classes first, while in model first you design the data model first and entities are generated based on it.</li> <li>based on a metadata model (EDMX) (although it is arguably absent from code first) which also defines mappings; the EDMX is an XML model containing the database structure, the entity structures and the mappings between them and is supported by a designer built into Visual Studio. In code-first, mappings are defined in code rather than in EDMX.</li> <li>supports multiple database technologies (I've used MySql and Oracle).</li> <li>based on T4 code generation (in v4), which besides allowing for interesting extensibility scenarios, can generate: <ul> <li>entities derived from a base class specific to Entity Framework (EntityObject) </li> <li>POCO entities which don't depend on Entity Framework at all</li> <li>self-tracking entities. </li> </ul></li> <li>works well with RIA services (Silverlight).</li> <li>supports pretty much all relationship types I think, and inheritance with multiple strategies (although there may be some problems with some of them).</li> <li>very good support for Linq (Linq to Entities).</li> </ul> <p>There's also LLBLGen, which I haven't used, but from the comments of one of my co-workers it doesn't stand up as great.</p> <p>I've used NHibernate before, albeit briefly, and the impression was good; even though back then it wasn't as mature as it is now, it was still a very good library. Not sure if I had to choose between NH and EF now... I think I'd go with EF because that's what I've been using for the last year or so and development would go faster (for me alone), but feature-wise NH may be slightly better off.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload