Re: Best pracise for using Linq within a 3 Tier project
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.
Re: Best pracise for using Linq within a 3 Tier project
>>
>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.
Comment