TransactedReceiveScope Class

.NET Framework (current version)

The .NET API Reference documentation has a new home. Visit the .NET API Browser on to see the new experience.

An activity which scopes the lifetime of a transaction which is initiated by a received message. The transaction may be flowed into the workflow on the initiating message, or be created by the dispatcher when the message is received.

Namespace:   System.ServiceModel.Activities
Assembly:  System.ServiceModel.Activities (in System.ServiceModel.Activities.dll)


public sealed class TransactedReceiveScope : NativeActivity


Initializes a new instance of the TransactedReceiveScope class.


Gets or sets the Activity that makes up the body of the TransactedReceiveScope activity.


Gets the identifier of the cache that is unique within the scope of the workflow definition.(Inherited from Activity.)


Gets or sets an optional friendly name that is used for debugging, validation, exception handling, and tracking.(Inherited from Activity.)


Gets an identifier that is unique in the scope of the workflow definition.(Inherited from Activity.)


Gets or sets the implementation version of the activity.(Inherited from NativeActivity.)


Gets or sets the Receive activity associated with this TransactedReceiveScope activity.


Gets the collection of Variable associated with this TransactedReceiveScope.


Determines whether the specified object is equal to the current object.(Inherited from Object.)


Serves as the default hash function. (Inherited from Object.)


Gets the Type of the current instance.(Inherited from Object.)


Indicates whether the DisplayName property should be serialized.(Inherited from Activity.)


Returns a String that contains the Id and DisplayName of the Activity.(Inherited from Activity.)

The TransactedReceiveScope activity enables you to control the lifetime of the flowed transaction.


For an initiating TransactedReceiveScope activity (a TransactedReceiveScope that contains a Receive activity with CanCreateInstance set to true), the transaction is created before the runtime starts to execute the TransactedReceiveScope activity. This transaction is not ambient at the workflow activity layer, but it is ambient in the underlying persistence layers. If execution of the workflow encounters a Persist activity before the TransactedReceiveScope activity, the runtime tries to persist under the ambient transaction. This behavior causes a block until the transaction is completed. Because the workflow execution has not reached the Body section, the transaction cannot finish. This deadlock causes the workflow to stop responding until the transaction times out. When the transaction times out, the newly created instance is aborted.


Whenever you use a TransactedReceiveScope it is recommended to place all Receives in the workflow within TransactedReceiveScope activities.


When using TransactedReceiveScope and messages arrive in the incorrect order, the workflow will be aborted when trying to deliver the first out of order message. You must make sure your workflow is always at a consistent stopping point when the workflow idles. This will allow you to restart the workflow from a previous persistence point should the workflow be aborted.

The following example shows how to use the TransactedReceiveScope class in a Sequence activity.

return new Sequence
    Activities = 
        new WriteLine { Text = "Service workflow begins." },

        new System.ServiceModel.Activities.TransactedReceiveScope
            Variables = { requestMessage, replyMessage },
            Request = receive,
            Body = new Sequence
                Activities =
                    new WriteLine { Text = new InArgument<string>("Server side: Receive complete.") },

                    new WriteLine { Text = new InArgument<string>(new VisualBasicValue<string>() { ExpressionText = "\"Server side: Received = '\" + requestString.toString() + \"'\"" }) },

                    new PrintTransactionInfo(),

                    new Assign<string>
                        Value = new InArgument<string>("Server side: Sending reply."),
                        To = new OutArgument<string>(replyMessage)

                    new WriteLine { Text = new InArgument<string>("Server side: Begin reply.") },

                    new SendReply
                        Request = receive,
                        Content = SendContent.Create(new InArgument<string>(replyMessage)),                                    

                    new WriteLine { Text = new InArgument<string>("Server side: Reply sent.") },

        new WriteLine { Text = "Server workflow ends." },

.NET Framework
Available since 4.0

Any public static ( Shared in Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.

Return to top