for RuBoard |
Yesterday you learned about the various components that make up a .NET Data Provider and how those components rely on base classes and interfaces provided by ADO.NET. Two of the most important of those components are the connection and transaction objects that handle the communication between a provider and a data store and allow multiple statements to be executed as a logical unit of work against the data store, respectively. The command and transaction objects are presented first because they are the first objects you would naturally use when writing code to access a data store.
Specifically, today you'll learn the following concepts:
How to open and close connections to a data store and how to handle events
How to specify connection strings and abstract them for different types of applications
How connection pooling is exposed and can be used with connection objects in the SqlClient and OleDb providers
How to create and manage transactions in local and distributed environments
for RuBoard |