views:

93

answers:

1

I created a small VS solution that includes WF with WCF ReceiveActivity project (using basicHttpBinding) and a number of plain C# services. They all work perfectly when tested from VS 2008 using WCFTestClient.

I deployed them into a single Windows Service. All but WF service work fine. I spent 6 hours browsing, but didn’t find a solution that works. Please help.

+1  A: 

You should be using the WorkflowServiceHost instead of the normal ServiceHost. The WorkflowServiceHost does all the usual WCF related stuff but also makes sure a workflow runtime is created and the required workflow routing environment is setup.

See this blog post for how to do so. This second post show a bit more about how to change the configuration.

BTW. In general you should be using the context bindings like the basicHttpContextBinding and wsHttpContextBinding as they pass the context information containing the workflow instanceId with the messages.

Maurice
The Answer from Maurice and the links he provided closed the question.Thank you Maurice. You disserve all points repeated to this post
ablei2000