Day 15. Using ADO.NET in a Multi-Tier Application

for RuBoard

Day 15. Using ADO.NET in a Multi- Tier Application

Today, the start of Week 3, you begin the home stretch on your journey through ADO.NET. In the past two weeks, you learned in detail about the two major components of ADO.NET, the DataSet and .NET Data Providers. This week, you will apply the knowledge you've gained to design and implement applications using ADO.NET.

The basic design approach that we'll discuss today, a multi-tier (or n-tier ) approach, is one that is probably either explicitly or implicitly familiar to you. As you learned on Day 1, "ADO.NET in Perspective," this approach has been widely adopted in the industry because it provides a maintainable and extensible architecture for distributed enterprise applications.

Today's short lesson will focus on the multi-tier architecture in depth to make sure that you understand where ADO.NET fits in and how it can be used. Specifically, you'll learn

• The reasons you might design applications with a multi-tier architecture

• How a multi-tier architecture relates to distributed applications

• Where ADO.NET fits into the tiers of a multi-tier application

for RuBoard