This documentation is archived and is not being maintained.

TransactionScope::Dispose Method

Ends the transaction scope.

Namespace:  System.Transactions
Assembly:  System.Transactions (in System.Transactions.dll)

virtual void Dispose() sealed



Calling this method marks the end of the transaction scope. If the TransactionScope object created the transaction and Complete was called on the scope, the TransactionScope object attempts to commit the transaction when this method is called.

The use of the C# using construction ensures that this method is called even if an exception occurs. Exceptions that occur after calling this method may not affect the transaction. This method also restores the ambient transaction to it original state. A TransactionAbortedException is thrown if the transaction is not actually committed.

This method is synchronous and blocks until the transaction has been committed or aborted. Because of this, you should be extremely careful when using this method in a Windows Form (WinForm) application, or a deadlock can occur. If you call this method inside one WinForm Control event (for example, clicking a button), and use the synchronous Invoke method to direct the control to perform some UI tasks (for example, changing colors) in the middle of processing the transaction, a deadlock will happen. This is because the Invoke method is synchronous and blocks the worker thread until the UI thread finishes its job. However, in our scenario, the UI thread is also waiting for the worker thread to commit the transaction. The result is that none is able to proceed and the scope waits indefinitely for the Commit to finish. You should use BeginInvoke rather than Invoke wherever possible, because it is asynchronous and thus less prone to deadlock.

For more information on how this method is used, see the Implementing An Implicit Transaction Using Transaction Scope topic.

The following example demonstrates how to use the TransactionScope class to define a block of code to participate in a transaction.

No code example is currently available or this language may not be supported.
'  This function takes arguments for 2 connection strings and commands to create a transaction  
'  involving two SQL Servers. It returns a value > 0 if the transaction is committed, 0 if the  
'  transaction is rolled back. To test this code, you can connect to two different databases  
'  on the same server by altering the connection string, or to another 3rd party RDBMS   
'  by altering the code in the connection2 code block. 
Public Function CreateTransactionScope( _
  ByVal connectString1 As String, ByVal connectString2 As String, _
  ByVal commandText1 As String, ByVal commandText2 As String) As Integer 

    ' Initialize the return value to zero and create a StringWriter to display results. 
    Dim returnValue As Integer = 0
    Dim writer As System.IO.StringWriter = New System.IO.StringWriter

    ' Create the TransactionScope to execute the commands, guaranteeing 
    '  that both commands can commit or roll back as a single unit of work. 
        Using scope As New TransactionScope()
            Using connection1 As New SqlConnection(connectString1)
                ' Opening the connection automatically enlists it in the  
                ' TransactionScope as a lightweight transaction.

                ' Create the SqlCommand object and execute the first command. 
                Dim command1 As SqlCommand = New SqlCommand(commandText1, connection1)
                returnValue = command1.ExecuteNonQuery()
                writer.WriteLine("Rows to be affected by command1: {0}", returnValue)

                ' If you get here, this means that command1 succeeded. By nesting 
                ' the using block for connection2 inside that of connection1, you 
                ' conserve server and network resources as connection2 is opened 
                ' only when there is a chance that the transaction can commit.    
                Using connection2 As New SqlConnection(connectString2)
                    ' The transaction is escalated to a full distributed 
                    ' transaction when connection2 is opened.

                    ' Execute the second command in the second database.
                    returnValue = 0
                    Dim command2 As SqlCommand = New SqlCommand(commandText2, connection2)
                    returnValue = command2.ExecuteNonQuery()
                    writer.WriteLine("Rows to be affected by command2: {0}", returnValue)
                End Using 
            End Using 

        ' The Complete method commits the transaction. If an exception has been thrown, 
        ' Complete is called and the transaction is rolled back.
        End Using 
    Catch ex As TransactionAbortedException
        writer.WriteLine("TransactionAbortedException Message: {0}", ex.Message)
    Catch ex As ApplicationException
        writer.WriteLine("ApplicationException Message: {0}", ex.Message)
    End Try 

    ' Display messages.

    Return returnValue
End Function

Windows 7, Windows Vista, Windows XP SP2, Windows XP Media Center Edition, Windows XP Professional x64 Edition, Windows XP Starter Edition, Windows Server 2008 R2, Windows Server 2008, Windows Server 2003, Windows Server 2000 SP4, Windows Millennium Edition, Windows 98

The .NET Framework and .NET Compact Framework do not support all versions of every platform. For a list of the supported versions, see .NET Framework System Requirements.

.NET Framework

Supported in: 3.5, 3.0, 2.0