2

For a couple of years, I've been using the three-tier architecture (Presentation, Logic and Data Layer) to write applications. Usually, I am using tools such as .netTiers to generate the data layer and partially the logic layer. Everything is well defined and I love it.

I am now constraint to use LINQ to Entites (it appears that LINQ to SQL was abandoned by Microsoft) and I am really confused. It looks to me like the code generated by LINQ to Entites is a big mix of the logic and data layer on which I have very little control. In addition, I don't really like the fact that I have to use the classes (entities...) generated.

In the end, could you share your experiences and best practices with LINQ to Entities? Any idea how I could still have a well defined Three-Tier architecture?

Thanks!

Martin
  • 39,309
  • 62
  • 192
  • 278
  • I would really love to read where you found this information ? "(it appears that LINQ to SQL was abandoned by Microsoft) " – Shiva May 08 '09 at 17:55
  • 1
    http://www.infoq.com/news/2008/11/DLINQ-Future We would not like to invest in a dying technology. – Martin May 08 '09 at 22:02

2 Answers2

2

Ian Cooper wrote good series about architecting application using Linq2Sql:

Hope you find what you need.

Marek Tihkan
  • 1,914
  • 13
  • 11
2

L2S is not dead, but it is basically complete. Its an implementation ( Sql Adapter ) for Linq. Linq is a language feature and will continue to expand as .net versions are released.

What makes Linq beautiful is the simplicity. I for one, beyond additional providers ( like MySql, Firebird, etc... ) I don't really want them to muck it up.

Serapth
  • 7,122
  • 4
  • 31
  • 39