What to do and what NOT to do in each layer of your applicationhttp://blogs.mconstantin.eu.org/cchrism/archive/2004/06/02/152.aspxScott postedA 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.en-USCommunityServer 2.0 (Build: 60404.2676)re: What to do and what NOT to do in each layer of your applicationhttp://blogs.mconstantin.eu.org/cchrism/archive/2004/06/02/152.aspx#225Wed, 11 May 2005 21:08:00 GMT84fa4630-d7f3-4739-a4ce-65ab18add461:225Javier LunaI believe that any DataLayer must be a simple code block, that they allow operations against DB. <br> <br>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. <br> <br>Finally, I invite to you to download the DataLayer.Primitives Public Version. <br> <br>This is very cool Data Layer :) <br> <br>DataLayer.Primitives - Readme! <br><a target="_new" href="http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=1389">http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=1389</a> <br>