On the WF ReceiveActivity and WCF bindings

WF RFQ/RFS Negotiation Thoughts « Tales from a Trading Desk

WF RFQ/RFS Negotiation Thoughts « Tales from a Trading Desk — Mon, 05 Jan 2009 22:38:25 GMT

Pingback from WF RFQ/RFS Negotiation Thoughts « Tales from a Trading Desk

re: On the WF ReceiveActivity and WCF bindings

Maurice — Wed, 22 Oct 2008 05:25:48 GMT

What where you using as the host application when using the NetMsmqBinding?

Normally with the WCF/WF bridge you need to be using one of the context bindings. These not only make sure the workflow instanceId is routed but also add the behavior that creates and manages the WF runtime. So no context binding means no correlation and no runtime.

With any luck using MSMQ with WF should become a supported scenario in the future though. Stay tuned for more after the PDC.

re: On the WF ReceiveActivity and WCF bindings

Tegan — Tue, 21 Oct 2008 20:12:10 GMT

Actually, you CAN use a NetMsmqBinding with WF. I've done it. Just mark the contract as OneWay and set the initial RecieveActivity to implement it.

Unfortunately, you still can't use a NetMsmqBinding on the initial receive activity if you're hosting the WCF service in IIS. Some combination of WCF, MSMQ, WF, and WAS (activation services) doesn't let a workflow be activated by receipt of an MSMQ message.