N-Tier Applications and .NET: Achieving Isolation between UI and BOL
I love to create application developing in a n-tier... I have seen this article.
In the previous three articles we have seen how a typical 3-tier application looks like and how to achieve isolation between Data Access Layer and Business Object Layer. I mentioned in the last article that we still have tight coupling between UI and database. This is due to the fact that our Select methods are returning DataSets which contain actual database column names. This means any change to database column names is going to affect UI layer. This article takes the concept one step ahead and shows how this coupling can be reduced.
Click here to view more...
In the previous three articles we have seen how a typical 3-tier application looks like and how to achieve isolation between Data Access Layer and Business Object Layer. I mentioned in the last article that we still have tight coupling between UI and database. This is due to the fact that our Select methods are returning DataSets which contain actual database column names. This means any change to database column names is going to affect UI layer. This article takes the concept one step ahead and shows how this coupling can be reduced.
Click here to view more...
0 Comments:
Post a Comment
<< Home