Comments on: Finally, An example of a Multi tier architecture for Linq to Sql http://lukhezo.com/2008/02/12/finally-an-example-of-a-multi-tier-architecture-for-linq-to-sql/ .NET Haberdasher Thu, 22 Dec 2011 04:06:39 +0000 hourly 1 http://wordpress.com/ By: castalian http://lukhezo.com/2008/02/12/finally-an-example-of-a-multi-tier-architecture-for-linq-to-sql/#comment-25 Wed, 05 Mar 2008 08:06:42 +0000 http://castalian.wordpress.com/2008/02/12/finally-an-example-of-a-multi-tier-architecture-for-linq-to-sql/#comment-25 If you want a clean seperate data layer look at the first two lessons at http://www.asp.net/learn/data-access/. I have built smart and web clients to this architecture, your data layer should be ‘client’ agnostic.

At this moment in time Linq is immature and not suited to n-tier applications. I have just lost money building an application with it. The fact that you are having to ‘conjure up’ an implementation, and Microsoft have not, speaks volumes to me.

Yes Linq is powerful, but for business, I will wait for the ADO.NET entity framework (Astoria).

]]> By: harry http://lukhezo.com/2008/02/12/finally-an-example-of-a-multi-tier-architecture-for-linq-to-sql/#comment-24 Tue, 04 Mar 2008 16:22:49 +0000 http://castalian.wordpress.com/2008/02/12/finally-an-example-of-a-multi-tier-architecture-for-linq-to-sql/#comment-24 This solution is not supposed to be ‘easier than datasets’ it’s supposed to give you a properly separated datalayer which it does. Just because something is easier doesn’t necessarily make it desirable.
I should also point out that this solution is aimed specifically at Asp.Net applications, so your complaint about winforms is missing the point a bit.
Just my 2 cents…

]]>