In response to this post , Anderson raised the following question. Definitely too hard and not service-oriented.  I like the idea of sending it via the headers or some other such implementation, but that would also require implementation on the other...

When we start doing this two way style of messaging, we now open up to start modeling some interesting business problems.  In the previous post, you'll note that I did not include the code, because I mentioned we needed to be more clever in scenarios...

So, we've seen in part 1 how to manage context, we saw in part 2 how we can take that basic knowledge to do duplex messaging.  Once we start doing duplex work, there are some interesting patterns, and the first one is one that we like to call "long...

Martin posted an interesting question here on my last post: <quote> The first thing that we need to do in order to enable this duplex messaging to occur is that the "client" workflow has to explicitly provide its context token to the service...

A continuation of my series of demos from my advanced workflow services talk.  Here we focus on duplex message exchange patterns. Duplex messaging is something that we model at the application level (as opposed to the infrastructure level) because...

So, last week I wrapped up a conversation at TechReady, our internal conference, where I was talking about the integration between WF and WCF in .NET 3.5.  This talk was somewhat bittersweet, it's the last conference where I'm scheduled to talk about...

Late last night, the PDC team posted an additional "bunch" of sessions, including one I'm particularly interested in: Extending Windows Workflow Foundation v.Next with Custom Activities Presenter: Matt Winkler Windows Workflow Foundation (WF...