ER Diagrams, Domain Model, and N-Layer Architecture | ASP.NET 3.5 Application Architecture and Design

OMS Project using 2-Layer

We know that the default coding style in ASP.NET 2.0 already supports the 1-tier 1-layer style, with two sub-layers in the main UI layer as follows:

Designer code files: ASPX markup files
Code behind files: Files containing C# or VB.NET code

Because both of these layers contain the UI code, we can include them as a part of the UI layer. These two layers help us to separate the markup and the code from each other. However, it is still not advisable to have logical code, such as data access or business logic, directly in these code-behind files.

Now, one way to create an ASP.NET web application for our Order Management System (OMS) in just one layer is by using a DataSet (or DataReader) to fill the front-end UI elements directly in the code-behind classes. This will involve writing data access code in the UI layer (code-behind), and will tightly bind this UI layer with the data access logic, making the application rigid (inflexible), harder to maintain, and less scalable...

Tech Concepts

Programming languages

Tech Tools

Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.

Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.

50+ new titles added per month and exclusive early access to books as they are being written.

ASP.NET 3.5 Application Architecture and Design

By : Vivek Thakur

ASP.NET 3.5 Application Architecture and Design

By: Vivek Thakur

Overview of this book

OMS Project using 2-Layer

ASP.NET 3.5 Application Architecture and Design

By : Vivek Thakur

ASP.NET 3.5 Application Architecture and Design

By: Vivek Thakur

Overview of this book

OMS Project using 2-Layer

Confirmation

Buy this book with your credits?

Submit Your Feedback

Create a Free Account To Continue Reading

Sign in to activate your 7-day free access