LINQ
-
Would you consider LINQ as a Data access layer or business layer or all 2 of them? I mean how would you incorporate LINQ to the three layer design? I have done a research on this question and would like to know what you think.
-
Would you consider LINQ as a Data access layer or business layer or all 2 of them? I mean how would you incorporate LINQ to the three layer design? I have done a research on this question and would like to know what you think.
LINQ is a query syntax. Its not a layer.
Mark Churchill Director, Dunn & Churchill Pty Ltd Free Download: Diamond Binding: The simple, powerful, reliable, and effective data layer toolkit for Visual Studio.
Alpha release: Entanglar: Transparant multiplayer framework for .Net games. -
Would you consider LINQ as a Data access layer or business layer or all 2 of them? I mean how would you incorporate LINQ to the three layer design? I have done a research on this question and would like to know what you think.
Bassam Saoud wrote:
I mean how would you incorporate LINQ to the three layer design?
Very, very carefully. Really, to do this, you need to disconnect the data context, otherwise the temptation is there for you to retrieve data in completely the wrong places.
Deja View - the feeling that you've seen this post before.
-
Bassam Saoud wrote:
I mean how would you incorporate LINQ to the three layer design?
Very, very carefully. Really, to do this, you need to disconnect the data context, otherwise the temptation is there for you to retrieve data in completely the wrong places.
Deja View - the feeling that you've seen this post before.
Would you recommend I do that? I mean, from an architecture point of view, would you consider using LINQ in your project(s) vs the clean 3 layer architecture and traditional ADO.NET? sorry for not replying to your post earier, When you posted , I just voted it
-
Would you recommend I do that? I mean, from an architecture point of view, would you consider using LINQ in your project(s) vs the clean 3 layer architecture and traditional ADO.NET? sorry for not replying to your post earier, When you posted , I just voted it
Bassam Saoud wrote:
sorry for not replying to your post earier, When you posted , I just voted it
Don't worry about it.
Bassam Saoud wrote:
I mean, from an architecture point of view, would you consider using LINQ in your project(s) vs the clean 3 layer architecture and traditional ADO.NET?
Well, we wrote a lot of do just this, and the more time goes by, the less happy I am with it. It's just such a bloody mess - and there's a lot of unnecessary wrangling going on. I must admit that I am looking at us moving actively back to ActiveRecord - or possibly EF. We will still continue to use L4O though.
Deja View - the feeling that you've seen this post before.
-
Bassam Saoud wrote:
sorry for not replying to your post earier, When you posted , I just voted it
Don't worry about it.
Bassam Saoud wrote:
I mean, from an architecture point of view, would you consider using LINQ in your project(s) vs the clean 3 layer architecture and traditional ADO.NET?
Well, we wrote a lot of do just this, and the more time goes by, the less happy I am with it. It's just such a bloody mess - and there's a lot of unnecessary wrangling going on. I must admit that I am looking at us moving actively back to ActiveRecord - or possibly EF. We will still continue to use L4O though.
Deja View - the feeling that you've seen this post before.
Pete O'Hanlon wrote:
Well, we wrote a lot of do just this, and the more time goes by, the less happy I am with it. It's just such a bloody mess
Yeah, I totally agree, Its a mess. I have read some good articles though like this MSDN Article[^], but still I dont like. I hope you would write an article about your experience :-O
-
Pete O'Hanlon wrote:
Well, we wrote a lot of do just this, and the more time goes by, the less happy I am with it. It's just such a bloody mess
Yeah, I totally agree, Its a mess. I have read some good articles though like this MSDN Article[^], but still I dont like. I hope you would write an article about your experience :-O
I was going to give away the data layer that we wrote, but frankly it's becoming a bit embarrassing.
Deja View - the feeling that you've seen this post before.
-
I was going to give away the data layer that we wrote, but frankly it's becoming a bit embarrassing.
Deja View - the feeling that you've seen this post before.
Well I would love to see an article Why not to use Linq or This is is how to use Linq in a three tier layer. I am sure many will be intersted in your experience :-O