WorkflowInstanceID

If I understand what you are doing correctly - you are trying to execute a sequential workflow and then have it fire an event to another workflow. What you want to do is pass the guid of the statemachineworkflow as a parameter to the sequential workflow - and extract it from the OutputParameters property of WorkflowCompletedEventArgs.

I am pretty sure though you don't want to this this way. You don't want a statemachineworkflow subscribing to an event of the WorkflowRuntime. You can implement this all using a Host level service.

JonFlanders at 2007-9-10 >

1. On your sequential workflow, declare a public property for a workflow instance id.
2. In the state machine workflow, use the InvokeWorkflow activity to start your sequential workflow and then move to a state where you will wait for the response (i.e. you have a HandleExternalEvent activity - see the next step).
3. Define a local service interface with an event that signals the sequential workflow is done.
4. In your host code or the same local service as the previous step (this is a better option) register a handler for the workflow completed event.
5. In the handler for the completed event, use the event arguments to get the output parameters from the sequential workflow and get the instance ID parameter that points to the state machine workflow (this is the property you created in step 1).
6. Now, raise the event on the local service interface, making sure to use the state machine instance ID so the event gets routed to the correct instance.
7. The event handler in your state machine should take over and you'll know the sequential workflow is completed.

Matt

MattMilner-Pluralsight at 2007-9-10 >

I uploaded a simple example to http://www.masteringbiztalk.com/blogs/jon/content/binary/HostEventExample.zip

JonFlanders at 2007-9-10 >