Day 17. ADO.NET in the Data Services Tier

for RuBoard

As you learned yesterday , for your presentation services tier to be able to consume data, your data services tier needs to supply it. To that end, the data services tier is responsible for providing an interface through which both the presentation and business services tiers can interact. This approach abstracts the data access code from the other tiers and makes it possible to reuse the classes in other applications.

Today and tomorrow, you'll learn about designing the data access classes that live in the data services tier. You'll also learn how you can take advantage of implementation inheritance and other features of the .NET Framework to create a flexible and robust solution. Specifically, today you'll learn

How to design a base class for your data services tier for both serviced and non-serviced components
Strategies for incorporating custom exception handling and logging
How to design data access classes
How to abstract the creation of provider-specific objects
How to use pure .NET classes

for RuBoard