Hi,

Is there a way to check whether WorkflowRuntime instance exists in the appdomain?

And if it is, is there a way to get reference to the instance?

In some terms, I'd like to see the WorkflowRuntime as a service provided by hosting application (whatever it is). So, a component that starts a workflow is not the one that enables its execution ( = creates a host for workflows).

Thanks,

Mark

As far as I know the only way to test if there is a WorkflowRuntime in your AppDomain is to try to create an instance. You will receive an InvalidOperationException if there is already one in the AppDomain.

And the only way I know of to get a reference to the existing instance is for your host application to keep one in a well known place. For example, the ASP.NET samples keep a reference to the WorkflowRuntime instance in the WorkflowWebRequestContext system type.

You can grab the ASP.NET sample at www.windowsworkflow.net.

Cheers,
Paul

Paul,

I'm very curious regarding your vision of workflows integration into business layers of enterprise systems.

What actually would be a host for WorkflowRuntime? I expected that your team should provide more convenient way to control the lifetime of WorkflowRuntime object.

Ok, it's not that big deal to solve this issue - it looks like everybody who's making few steps away of the Samples will have to do it.

The model with 1 WorkflowRuntime object per appdomain is clear and great when you execute workflows from console application or winforms application.

But when workflows should be launched right behind the service interfaces layer it becomes complicated. At least, it looks that way to me.

Can you elaborate regarding some design considerations that you think should be taken while developing/integrating workflows into business logic layer?

Thanks,

Mark