Contains classes that allow you to write your own transactional application and resource manager. Specifically, you can create and participate in a transaction (local or distributed) with one or multiple participants.
Classes Structs Interfaces IDtcTransactionDescribes a DTC transaction.
IEnlistmentNotificationDescribes an interface that a resource manager should implement to provide two phase commit notification callbacks for the transaction manager upon enlisting for participation.
IPromotableSinglePhaseNotificationDescribes an object that acts as a commit delegate for a non-distributed transaction internal to a resource manager.
ISimpleTransactionSuperiorRepresents a transaction that is not a root transaction, but can be escalated to be managed by the MSDTC.
ISinglePhaseNotificationDescribes a resource object that supports single phase commit optimization to participate in a transaction.
ITransactionPromoterDescribes a delegated transaction for an existing transaction that can be escalated to be managed by the MSDTC when needed.
Enums DelegatesThe System.Transactions infrastructure makes transactional programming simple and efficient throughout the platform by supporting transactions initiated in SQL Server, ADO.NET, MSMQ, and the Microsoft Distributed Transaction Coordinator (MSDTC). It provides both an explicit programming model based on the Transaction class, as well as an implicit programming model using the TransactionScope class, in which transactions are automatically managed by the infrastructure. It is highly recommended that you use the easier implicit model for development. To get started, see the Implementing An Implicit Transaction Using Transaction Scope topic. For more information on writing a transactional application, see Writing A Transactional Application.
System.Transactions also provides types for you to implement a resource manager. The transaction manager native to the System.Transactions infrastructure allows volatile resources or a single durable resource enlistment to commit or roll back efficiently. For more information on implementing a resource manager, see Implementing A Resource Manager.
The transaction manager also transparently escalates local transactions to distributed transactions by coordinating through a disk-based transaction manager like the DTC, when an additional durable resource manager enlists itself with a transaction. There are two key ways that the System.Transactions infrastructure provides enhanced performance.
Dynamic Escalation, which means that the System.Transactions infrastructure only engages the MSDTC when it is actually required for a transaction. This area is covered in depth in the Transaction Management Escalation topic.
Promotable Enlistments, which allows a resource, such as a database, to take ownership of the transaction if it is the only entity participating in the transaction. Later, if needed, the System.Transactions infrastructure can still escalate the management of the transaction to MSDTC. This further reduces the chance of using the MSDTC. This area is covered in depth in the Optimization Using Single Phase Commit and Promotable Single Phase Notification topic.
For more information on how to use the System.Transactions namespace, see Transaction Processing.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4