I use a " code-first, database-last " development process with LINQ, where I create my Entity classes by hand, add business logic (carefully using partial classes), and unit test them. Once I'm happy with things, I'll add the database tables and do the mapping. This is simply works better than a "database-first, code last" development process for me. I've had some challenges using DLINQ along the way. Bottom-line is, I would like to write my business logic to use an in-memory
Read More...