|
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.
|
|
|
|
|
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.
|
|
|
|
|
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.
|
|
|
|
|
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
|
|
|
|
|
I was going to give away the data layer that we wrote, but frankly it's becoming a bit embarrassing.
|
|
|
|
|
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
|
|
|
|
|
When should a class access its own data members through a property rather than directly access them?
|
|
|
|
|
Only when you really need to. Accessing through the property involves more work in the IL than actually directly accessing them.
|
|
|
|
|
Pete O'Hanlon wrote: Only when you really need to.
Ok, then when do you really need to?
led mike
|
|
|
|
|
CodingYoshi wrote: When should a class access its own data members through a property rather than directly access them?
Never. There is no such thing as "property" in C++.
led mike
|
|
|
|
|
When your property methods contain logic that maintains some other value when the property changes. The alternative is to duplicate that logic ( ) wherever you directly change the property value.
|
|
|
|
|
|
Brady Kelly wrote: When your property methods contain logic that maintains some other value when the property changes. The alternative is to duplicate that logic ( [Unsure] ) wherever you directly change the property value.
That's why I would always access a data member through the property, if one is provided by the class designer. Even if it appears that accessing the member directly would accomplish the same thing, you don't know what what might be added to the property later. That's what properties are for; to provide controlled access to a data member. Why circumvent it?
Robert C. Cartaino
|
|
|
|
|
Just when they need to.
"The clue train passed his station without stopping." - John Simmons / outlaw programmer
"Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon
"Not only do you continue to babble nonsense, you can't even correctly remember the nonsense you babbled just minutes ago." - Rob Graham
|
|
|
|
|
Hi All! I am new to the forum and am hoping you can help with finding a simple source code management software. I've tried downloading older open source versions but either the websites weren't running anymore or the code was for Linux or something. I am running Windows Vista...Other programs I found online were either designed for a server or too much money.
I just want a simple code management program with check in/out functionality, some basic version tracking capability and to be able to export the database for easy backup.
Is there any software like this that is free?
Thanks for your help!
|
|
|
|
|
Subversion[^] comes to mind.
There are a few free version management applications discussed here[^].
|
|
|
|
|
I'll second that.
"The clue train passed his station without stopping." - John Simmons / outlaw programmer
"Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon
"Not only do you continue to babble nonsense, you can't even correctly remember the nonsense you babbled just minutes ago." - Rob Graham
|
|
|
|
|
I have used Perforce - I believe a 1 or 2-user license is free.
HTH
|
|
|
|
|
I'm trying Perforce. It runs good I'm just trying to figure out how to use it. Not sure of the funtions of different views.
It actually does exactly what I hoped I could. I already have server and client on my home computer and I plan to setup a client version on my work computer. running over the internet.
Hopefully it all works. Looks good though.
Thanks!
|
|
|
|
|
I use VisualSVN, the server is free and is subversion based. TortouiseSVN is the good for the client side and is free as well. VisualSVN provides a low cost Visual Studio plug in that runs on top of TortuoiseSVN that I think is well worth it.
|
|
|
|
|
Netblue wrote: VisualSVN
That is really nice to add to subversion
"The clue train passed his station without stopping." - John Simmons / outlaw programmer
"Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon
"Not only do you continue to babble nonsense, you can't even correctly remember the nonsense you babbled just minutes ago." - Rob Graham
|
|
|
|
|
Ankh 2.0 is a free source control provider for VS if you are running SVN > 1.5. Don't bother with Ankh 1 though
|
|
|
|
|
SourceVault is free for single-user
|
|
|
|