Patterns & Practices

In last two posts, I have been talking about the layered architecture in ASP.NET applications. If you missed them, you might want to read the first part and the second part, just to get a better insight on the topic I am discussing today.Dividing an application into multiple layers helps to: Keep different concerns of components separate so that there is clear distinction between different parts e.g. keeping presentation and business logic separate...

Read More

Introducing Business Objects

This is the second part of discussion on layered architecture in ASP.NET applications. I will extend the same examples, so you should read the first part here, or at least glance through the examples. Let us extend the data access layer class to include a method to update the database. ProductDataAccessLayer.cs using System; using System.Data; using System.Data.SqlClient; using System.Configuration; public class ProductDataAccessLayer { string...

Read More

Layered architecture for ASP.NET applications

This is the first post in a series of discussion on using layered architecture in ASP.NET applications. I will start with the basics and try to elaborate concepts gradually so as to help developers who have just begun to understand the concept of layers in an application. For quite a while, a tiered approach towards developing an application has been in the buzz. We hear people talking 2-tier, 3-tier, n-tier applications! What is a “tier” here?...

Read More