Enrique Gonzalez

Ron, first of all great post, secondly, maybe not the most accurate tittle, more than loading workflows definitions form the DB (.xaml file content) or any other way that it can  be turned into some string value using the DynamicActivity method i.e:

var activity = ActivityXamlServices.Load(new StringReade(wokflowToExecute)) as DynamicActivity;

This is an elegant workaround to implement service partitioning on WF, back in the
beta I asked something like that http://social.msdn.microsoft.com/Forums/en/wfprerelease/thread/41ecf7c5-8c74-4ec9-9bdf-437015b17ceb

The "limitation" of one WorkflowServiceHost per WF service is one of the reasons I decided to no
use WF services on one of our company's main solutions, given the number of services to implement, using WCF routing wouldn't be as practical or maybe not a clean, and using pick activities would be irrational, so we used plain WCF instead.

Currently we have another interesting scenario and the approach you're following gives me another option on how to handle this situation, so, thanks Ron and keep up the good stuff coming.

For me Workflow services is a mixed bag, there are few things I’m not willing to trade off :

-Contract First: it’s just awkward, I want be able to declare the service contract and then pick the operation to implement in the receive shape.

-I want to be able to group workflows as service operations instead of independent services, for example in the video you have HRService, what if I want to have a single  workflow for process the application , other dedicated to check the application status, other for vacation request, other for raise request, other for complains  and so on, all related to HRServices however I can’t host all of  them under http://localhost:8080/HRservices and “see” them as operations( ProcessApplication, CheckApplicationStatus, VacationRequest, RaiseRequest, Complains )  I’ll have to host each of them under different addresses and treat them as separate services, in other words I’ll end up having for example:

 http://localhost:8080/ProcessApplication

http://localhost:8081/CheckApplicationStatus

http://localhost:8082/VacationRequest

http://localhost:8083/RaiseRequest

http://localhost:8083/Complains

To accomplish the desire functionality (single service many operation) today we have to use parallel/ pick shapes which again doesn’t feel natural.

Just my thoughts, other than that; thanks and keep up the good work

Enrique G.

oh! man... thanks for the intention though,

BTW, pure speculation but I’m guessing that “soon”= Tech·Ed (May 11-15)

When are we, simple mortals, will be able to get our hands on it?
I could use something like your VPC ->