 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
.NET Forum / Languages / C# / March 2008Best pracise for using Linq within a 3 Tier project
Hi all What is the recommended way for using Linq within a 3 Tier project? Many thanks Ilyas, Do you mean a multilayer solution?. However for that is as well AFAIK the best solution, don't use LINQ. This because Linq is an expression language meant to get fast extractions from data and submit the changes to the database in a simple way. Cor > Do you mean a multilayer solution?. > > However for that is as well AFAIK the best solution, don't use LINQ. This > because Linq is an expression language meant to get fast extractions from > data and submit the changes to the database in a simple way. 1) LINQ isn't just meant for databases 2) I don't see how your description of LINQ (to SQL) in any way makes it unsuitable for multilayer solutions  SignatureJon Skeet - <skeet@pobox.com> http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet World class .NET training in the UK: http://iterativetraining.co.uk >> However for that is as well AFAIK the best solution, don't use LINQ. This >> because Linq is an expression language meant to get fast extractions from >> data and submit the changes to the database in a simple way. > > 1) LINQ isn't just meant for databases Did I write that? > 2) I don't see how your description of LINQ (to SQL) in any way makes > it unsuitable for multilayer solutions Did I say so, I thought that the general opinion was that it is not the "best" practise for multilayer solutions. Cor > >> However for that is as well AFAIK the best solution, don't use LINQ. This > >> because Linq is an expression language meant to get fast extractions from [quoted text clipped - 3 lines] > > Did I write that? Read what you wrote - there's no real need to mention databases at all in my view. Your statement is biased towards databases when I'd just say that LINQ is a set of technologies to ease data access, whatever the data source. > > 2) I don't see how your description of LINQ (to SQL) in any way makes > > it unsuitable for multilayer solutions > > Did I say so You said that if you want the best solution, don't use LINQ. That sounds like you feel it's unsuitable. > I thought that the general opinion was that it is not the > "best" practise for multilayer solutions. I don't think so. You may not use it in all layers (although LINQ to Objects is almost always useful, IMO) but there's nothing wrong with using LINQ in multi-layer solutions. You still need to solve a lot of the same problems as before in terms of concurrent updates etc, but LINQ will help in various ways. SignatureJon Skeet - <skeet@pobox.com> http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet World class .NET training in the UK: http://iterativetraining.co.uk On Mar 18, 6:05 am, "Cor Ligthert [MVP]" <notmyfirstn...@planet.nl> wrote: > Did I say so, I thought that the general opinion was that it is not the > "best" practise for multilayer solutions. No, that would be the opposite of the general opinion.
Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.