Hosting a Workflow in a Local Executable using Workflow Services Part III

<!--coloro:black--><span style="color:black <!--/coloro--><!--fonto:Verdanasans-serif--> Verdanasans-serif <!--/fonto--><!--sizeo:2--><span style="font-size:10pt;line-height:100% <!--/sizeo-->When the Windows Workflow Foundation (WF)*was first introduced in the .NET Framework 3.0, the only way to host a workflow in a client application was to use the <b><!--fonto:Verdanasans-serif--> Verdanasans-serif <!--/fonto-->WorkflowRuntime<!--fontc--><!--/fontc--></b> class programmatically, start the runtime, and create/start an instance of a workflow.* Furthermore, if you wanted to communicate between the client code and the workflow logic, you needed to ues a <b><!--fonto:Verdanasans-serif--> Verdanasans-serif <!--/fonto-->ExternalDataExchangeService<!--fontc--><!--/fontc--></b>.* This required a fair amount coding effort to get even the simplest of workflows up and running.* The .NET Framework 3.5 introduced <!--sizec--><!--/sizec--><!--sizeo:2--><span style="font-size:10pt;line-height:100% <!--/sizeo--> which are Windows Communication Foundation (WCF) Services authored as workflows.* Workflow Services give you a new way to accomplish this scenario using a much simpler,*cleaner, and arguably more elegant approach.* In this three part screencast, I show you how to improve on the more*manual hosting + ExternalDataExchangeServices approach to hosting a workflow in a client executable*using Workflow Service*by:<!--sizeo:0--><span style="font-size:12pt;line-height:100% <!--/sizeo--><!--fontc--><!--/fontc--><!--colorc--><!--/colorc-->
<!--coloro:black--><span style="color:black <!--/coloro--><!--fonto:Verdanasans-serif--> Verdanasans-serif <!--/fonto--><!--sizeo:2--><span style="font-size:10pt;line-height:100% <!--/sizeo-->Part I - Reviewing the SimpleExpenseReport application from the <!--sizec--><!--/sizec--><!--sizeo:2--><span style="font-size:10pt;line-height:100% <!--/sizeo--> tutorial so we can compare the two approaches.* The application explicitly hosts the WorkflowRuntime & uses ExternalDataExchangeService

Part II - <!--sizec--><!--/sizec--><!--fontc--><!--/fontc--><!--colorc--><!--/colorc--><!--coloro:black--><span style="color:black <!--/coloro--><!--fonto:Verdanasans-serif--> Verdanasans-serif <!--/fonto--><!--sizeo:2--><span style="font-size:10pt;line-height:100% <!--/sizeo-->Walking through the fundamentals of creating a Workflow Service and h<!--sizec--><!--/sizec--><!--fontc--><!--/fontc--><!--colorc--><!--/colorc--><!--coloro:black--><span style="color:black <!--/coloro--><!--fonto:Verdanasans-serif--> Verdanasans-serif <!--/fonto--><!--sizeo:2--><span style="font-size:10pt;line-height:100% <!--/sizeo-->osting the Workflow Service locally<!--sizec--><!--/sizec--><!--fontc--><!--/fontc--><!--colorc--><!--/colorc-->
<!--coloro:black--><span style="color:black <!--/coloro-->[/COLOR]<!--fonto:Verdanasans-serif--> Verdanasans-serif <!--/fonto--><!--sizeo:2--><span style="font-size:10pt;line-height:100% <!--/sizeo--> - Walking through my rewrite of the SimpleExpenseReport application using Workflow Services.

Source code for the Workflow Services version of SimpleExpenseReport is available*at .<!--sizec--><!--/sizec--><!--fontc--><!--/fontc--><!--colorc--><!--/colorc-->
<!--sizec--><!--/sizec--><!--sizec--><!--/sizec-->.