Comments on: Building a Generic DAO / Repository with LINQ http://erichauser.net/2007/11/08/building-a-generic-dao-repository-with-linq/ J2EE, .NET, and general technology Fri, 30 Oct 2009 01:03:14 +0000 http://wordpress.org/?v=2.8.5 hourly 1 By: Where is IDataContext? « maonet technotes http://erichauser.net/2007/11/08/building-a-generic-dao-repository-with-linq/comment-page-1/#comment-49 Where is IDataContext? « maonet technotes Fri, 18 Jan 2008 21:36:18 +0000 http://www.hausertechnologies.com/wordpress/?p=36#comment-49 [...] this interesting blog, building Generic DAO using Linq to SQL, idea is identical to NHibernate’s DAO. By doing this, we will have an option to operate data [...] [...] this interesting blog, building Generic DAO using Linq to SQL, idea is identical to NHibernate’s DAO. By doing this, we will have an option to operate data [...]

]]> By: Adam Cooper http://erichauser.net/2007/11/08/building-a-generic-dao-repository-with-linq/comment-page-1/#comment-48 Adam Cooper Wed, 05 Dec 2007 21:26:02 +0000 http://www.hausertechnologies.com/wordpress/?p=36#comment-48 Eric, This is excellent, excellent work. I only wish there were more to read. I'm in the middle of re-developing and re-architecting an online store using LINQ to SQL, but I'm struggling to know where to draw the line on who should have access to the DataContext. I keep coming back to the conclusion that I should use a repository pattern to shield the application from directly working with the DAL that I'm generating with sqlmetal. But the question I keep coming to is "How do I abstract away the use of the DataContext without having to write a lot of redundant object wrappers around my sqlmetal DAL?" Your blog post here is the closest thing I've found to an answer, though I'm still uncertain about some of the details. Is there anything more that you can share? Could you provide downloadable code samples of what you're writing about here? Being able to browse the files and see the big picture would help me tremendously. Thanks much, Adam Cooper Eric,

This is excellent, excellent work. I only wish there were more to read.

I’m in the middle of re-developing and re-architecting an online store using LINQ to SQL, but I’m struggling to know where to draw the line on who should have access to the DataContext. I keep coming back to the conclusion that I should use a repository pattern to shield the application from directly working with the DAL that I’m generating with sqlmetal. But the question I keep coming to is “How do I abstract away the use of the DataContext without having to write a lot of redundant object wrappers around my sqlmetal DAL?”

Your blog post here is the closest thing I’ve found to an answer, though I’m still uncertain about some of the details. Is there anything more that you can share? Could you provide downloadable code samples of what you’re writing about here? Being able to browse the files and see the big picture would help me tremendously.

Thanks much,
Adam Cooper

]]>