View Single Post
  #1 (permalink)  
Old January 8th, 2013, 04:37 AM
dpant dpant is offline
Registered User
Points: 20, Level: 1
Points: 20, Level: 1 Points: 20, Level: 1 Points: 20, Level: 1
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
 
Join Date: Jan 2013
Posts: 5
Thanks: 0
Thanked 0 Times in 0 Posts
Default Agatha's and Linq to Sql

Hello,

First of all let me thank you for your excellent book.

I am used to building asp.net sites using the RAD approach with most of the logic found in the code behind. As a result, this book was both enlightening and shocking to me.

I really love the Agatha's project even though it took some time to understand how everything sticks together. My question is, can I use Linq to Sql instead of NHibernate? If so, does this mean I can avoid having to implement Unit of Work and Query Object since they are automatically provided by Linq to Sql?

On a side note, assuming I am using Linq to Sql, what is the best approach as far as the objects automatically created by the dbml designer are conserned? Should I take advantage of the partial classes or use mappers to convert between them and the domain model's objects?

Thank you very much in advance,
dimitris
Reply With Quote