Abstract: Sending or receiving messages in a host agnostic way in a continuation based runtime. A method includes defining a contract between a continuation based runtime and host for sending or receiving a message. The contract defines one or more of: details about what should be included in the messages, operations for sending the message; operations for receiving the message, parameters for cancellation of inflight operations, or notifications about correlation information lifetime. The method further includes identifying a correlation handle. The correlation handle uniquely identifies an executing instance of an activity. The method further comprises identifying a bookmark. The bookmark defines where the continuation based runtime should resume after sending or receiving the message. The method further comprises calling the contract using the correlation handle and the bookmark to allow the message to be correctly routed by the host and for the continuation based runtime to be correctly resumed.

Abstract: Sending or receiving messages in a host agnostic way in a continuation based runtime. A method includes defining a contract between a continuation based runtime and host for sending or receiving a message. The contract defines one or more of: details about what should be included in the messages, operations for sending the message; operations for receiving the message, parameters for cancellation of inflight operations, or notifications about correlation information lifetime. The method further includes identifying a correlation handle. The correlation handle uniquely identifies an executing instance of an activity. The method further comprises identifying a bookmark. The bookmark defines where the continuation based runtime should resume after sending or receiving the message. The method further comprises calling the contract using the correlation handle and the bookmark to allow the message to be correctly routed by the host and for the continuation based runtime to be correctly resumed.

Abstract: An automated workflow composable action model allows composition of actions into an activity flow. Activity flows can be based on an activity model, created on an ad hoc basis, or a combination of the two. A standard set of messages and interfaces provide flexibility and uniformity so that any of a wide variety of functionality can be easily integrated into the workflow services. Actions can encapsulate the logic for sending and receiving messages. Synchronization between actions can be supported.

Abstract: Workflow debugging. A debug engine integrated with an external development tool debugging framework sets breakpoints directly on workflow activities and stops execution of the workflow at each of the breakpoints. The state of the workflow activity at the breakpoint is displayed. The debug engine extracts source code of the workflow for debugging at the source code level.

Abstract: An automated workflow composable action model allows composition of actions into an activity flow. Activity flows can be based on an activity model, created on an ad hoc basis, or a combination of the two. A standard set of messages and interfaces provide flexibility and uniformity so that any of a wide variety of functionality can be easily integrated into the workflow services. Actions can encapsulate the logic for sending and receiving messages. Synchronization between actions can be supported.