Re: The Myth of 3-Tier
I am a big fan of making my own Full blown Custom Business objects or simple Domain objects that map directly to database tables, have a look at the Models project in the Pet Shop .net sample...
View ArticleRe: The Myth of 3-Tier
r_nassabeh3-Layered implies a division of responsibilities in logical components whereas in 3-Tier we privilege a physical division of activities. Take a look at...
View ArticleRe: The Myth of 3-Tier
3-Layered implies a division of responsibilities in logical components whereas in 3-Tier we privilege a physical division of activities. Take a look at...
View ArticleRe: The Myth of 3-Tier
Well, I'd think there is no clear standard generally approved difference between "tiered" and "layered" - eveybody has their own standards :)Have a look:...
View ArticleRe: The Myth of 3-Tier
'Tire' is used when talking about physical seperation of program components, 'layer' is used in logical seperation.
View ArticleRe: The Myth of 3-Tier
"The Myth of 3-Tier" is reality here - I do use 3-tier in fact even more tiers (or layers? :) ) architecture in real life asp.net applications, and this approach works well here. Yes, and no ADO.NET...
View ArticleRe: The Myth of 3-Tier
>For those people who abstract the logic to persist out of your business objects, how do you do it without DataSets? One guy here says there isn't an elegant way, another feels that the "Data...
View ArticleRe: The Myth of 3-Tier
Datasets do make more sense in a .NET environment; however, there is always the possibility of the tool becoming outdated as mentioned in a previous post. WIth ORM's and code generators though... DTO's...
View ArticleRe: The Myth of 3-Tier
Heh. I don't use DataSets at all as they seem too clunky and prohibitive to me. I generally use DataReaders and loop through them or, if I need to, load them into a typed List or array >:D It's...
View ArticleRe: The Myth of 3-Tier
Well it is usually a matter of preference. But I'm personnaly a fan of using Custom Business Entities instead of datasets for the following reasons:1. Dataset is a fairly complete and powerfull class,...
View ArticleRe: The Myth of 3-Tier
Well, 3-Tier is definitelly not a myth, I saw it a few times. :)Before using new framework, like Linq2Sql, we have to get a thorough understanding of how it works. More than that, we have to change the...
View ArticleRe: The Myth of 3-Tier
FevirVitaliy I agree with about entity objects, however the question then arises, do you actually have tiers, or do you have what Rocky Lhotka would call "Smart Business Objects" where the objects know...
View ArticleRe: The Myth of 3-Tier
Vitaliy I agree with about entity objects, however the question then arises, do you actually have tiers, or do you have what Rocky Lhotka would call "Smart Business Objects" where the objects know how...
View ArticleRe: The Myth of 3-Tier
Actually, DataSets fit better for short-term project. For long-term projects it's recommended to use Business Entities, Data Access layer and appropriate CRUD stored procedures. DataSets will never...
View ArticleRe: The Myth of 3-Tier
The debate I have heard about DataSets is not directly related to a 3-tier architechture, but rather how long that object will persist in the world of Microsoft. Imaginge 8 years ago designing an...
View ArticleRe: The Myth of 3-Tier
We ran into many problem with LINQ and our entities. You can query around quite easily, however it encourages you to simply go to the database for using LINQ rather than using the Entity object. We...
View ArticleRe: The Myth of 3-Tier
Data set is a framework thing; it's just a place to store data in a disconnected mode. While data sets/data tables may be used to fetch data from the database, for updates/inserts, we use stored procs...
View ArticleRe: The Myth of 3-Tier
Hi,I used DataSets for a while but since I worked with LINQ, I use the DataContext and Entity-Classes created by LINQ TO SQL as the Data access layer, and create a Business layer returning...
View ArticleThe Myth of 3-Tier
We've got a raging debate going on here at work, and I'm curious what you all think. From what you experienced developers here have seen, have you seen a 3 tier architecture (I'm talking...
View Article