Assembly: System.Transactions (in system.transactions.dll)
This class provides methods for transaction propagation. For more information on how this process works, see Transaction Propagation.
Using the methods provided by this class, you can engage in two types of transaction propagations, Export/Import (push model) and Transmitter/Receiver (pull model).
The Export/Import (push model) propagation involves these steps,
On the remote machine, obtain the "whereabouts" of the transaction manager of that machine by calling the GetWhereabouts method. You can then cache this piece of information on the client machine for future usage.
Send the data containing the whereabouts to the client machine using any preferred method
On the client machine, use the whereabouts to "export" the transaction to the remote machine and generate a transaction "cookie". This is done by calling GetExportCookie and passing in the remote machine's whereabouts.
Send the data containing the transaction "cookie" to the remote machine using any preferred method
On the remote machine, use the transaction "cookie" to obtain a clone of the client transaction by calling the GetTransactionFromExportCookie method.
The Transmitter/Receiver (pull model) propagation involves these steps,
On the client machine, using the transaction generates a corresponding "propagation token" by calling GetTransmitterPropagationToken
Send the data containing the "propagation token" of the transaction to the remote machine using any preferred method
On the remote machine, use the "propagation token" to obtain a clone of the client transaction by calling GetTransactionFromTransmitterPropagationToken
The Transmitter/Receiver model provides better performance in scenarios where the transaction token is sent to a remote machine, but the remote machine may not use it to obtain the transaction. This is because the transaction is not propagated until GetTransactionFromTransmitterPropagationToken is called. Another advantage is that the propagation token can be sent to any remote machine, while the export cookie can be used only on the machine that provided the whereabouts.
However, you should also note that the whereabouts of remote transaction managers are encapsulated in all the propagation tokens, making them bigger than the corresponding transaction cookies from the Export/Import model.
Note This type uses LinkDemand to prevent it from being called from untrusted code; however, only the immediate caller is required to possess the FullTrust permission set.
Windows 98, Windows Server 2000 SP4, Windows Millennium Edition, Windows Server 2003, Windows XP Media Center Edition, Windows XP Professional x64 Edition, Windows XP SP2, Windows XP Starter EditionThe Microsoft .NET Framework 3.0 is supported on Windows Vista, Microsoft Windows XP SP2, and Windows Server 2003 SP1.