Comments

Thanks - I'm glad to be back on C9.

@Eddie Tse: Absolutely - we will have some blog posts / sample code available soon.  Be sure to check out our Facebook page for more

@Andrew_Morton:Good point... perhaps I'll add that

@h464r:Sorry about that - fixed it.

Check the links again - everything is pointing at the right place now.

Sample code from this session available

• Windows Workflow Foundation (WF4) - Exploring State Machine
• Windows Workflow Foundation (WF4) - Silverlight / State Machine Workflow Service

You can store the workflow definitions in Oracle - I'm using Entity Framework 4.1 in my code so you would need a provider that works with Entity Framework.

However, at this time we do not have a Workflow persistence provider for Oracle.  You won't need this unless your workflows are long running.

Can provide a web.config with the VirtualPathProvider?  I didn't know that.

I wonder if you could support a VirtualDirectory and then place a web.config file in the VirtualDirectory with the config you need if that would work.

It would be worth a try.

I don't understand your comment about WorkflowServiceHost being limited.  It is no different than a WCF ServiceHost.  The WCF Service Host will host one service per host.  The WF WorkflowServiceHost will host one workflow per host.

However, you can have multiple services and workflow services in you web application.  In fact you don't really deal with the WorkflowServiceHost or ServiceHost classes unless you are self-hosting so they are just another part of the infrastructure most of the time.

• WCF services have a collection of operations
• WF services also have a collection of operations

The main difference is that the WF service can enforce a messaging protocol with certain operations being available only at certain times.

My guess is that if you can build your solution with WCF services you can also build it with workflow services.

The blog post mentioned in the episode is here.