Marius's Personal site

My personal blog & gallery
Welcome to Marius's Personal site Sign in | Join | Help
in Search

Blogging About .NET

What to do and what NOT to do in each layer of your application

Scott posted
A reminder on "Three/Multi Tier/Layer Architecture/Design" brought to you by my late night frustrations.

So, before writting DataLayer stuff in your .aspx page (or worse, open connections), please review the article. One interesting note. Usually due to lack of time, and need to deliver the product yesterday, communications between layers is made of datasets, which used properly are ok, but cannot be enforced easility to be read-only. So, beware of code that modifies datasets directly in your UI Layer.

Published Wednesday, June 02, 2004 9:42 AM by cchrism
Filed Under:

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS



cchrism said:

I believe that any DataLayer must be a simple code block, that they allow operations against DB.

That code block would not have to know on the Business Entities. Single to specialize it is to execute the operations (Store Procedures and SQL Sentences) against the engine DB (SQL, Oracle, DB2, etc.), with which this setting.

Finally, I invite to you to download the DataLayer.Primitives Public Version.

This is very cool Data Layer :)

DataLayer.Primitives - Readme!
May 11, 2005 2:08 PM

What do you think?


This Blog

Post Calendar

<June 2004>


Listed on BlogShares


Powered by Community Server, by Telligent Systems