- Microsoft Windows Workflow Foundation 4.0 Cookbook
- Andrew Zhu
- 366字
- 2021-04-13 17:00:36
In the previous tasks, we used the WorkflowInvoker.Invoke
method to start a workflow instance on the same thread as the main program. It is easy to use; however, in most real applications, a workflow should run on an independent thread. In this task, we will use WorkflowApplication to run a workflow instance.
- Create a workflow project:
Create a new Workflow Console Application under the
Chapter01
solution and name the project asUseWorkflowApplication
. - Author a workflow:
In the opening
Workflow1.xaml
designer, click on Arguments, create twoInt32
InArguments
for Number1 and Number2. Create anInt32 OutArgument
for Result. Add an Assign activity to the workflow designer panel. In the Assign activity, type Result=Number1+Number2. - Write code to host the workflow:
Open
Program.cs
file and change code as follow:using System; using System.Activities; using System.Activities.Statements; using System.Threading; using System.Collections.Generic; namespace UseWorkflowApplication{ class Program{ static void Main(string[] args){ AutoResetEvent syncEvent = new AutoResetEvent(false); IDictionary<string, object> input = new Dictionary<string, object>() { {"Number1",123}, {"Number2",456} }; IDictionary<string,object> output=null; WorkflowApplication wfApp = new WorkflowApplication(new Workflow1(),input); wfApp.Completed = delegate(WorkflowApplicationCompletedEventArgs e) { Console.WriteLine("Workflow thread id:"+ Thread.CurrentThread.ManagedThreadId); output = e.Outputs; syncEvent.Set(); }; wfApp.Run(); syncEvent.WaitOne(); Console.WriteLine(output["Result"].ToString()); Console.WriteLine("Host thread id:"+Thread.CurrentThread.ManagedThreadId); } } }
- Run it:
Set
UseWorkflowApplication
asStartup
project. Press Ctrl+F5 to build and run the workflow without debugging. The application should run in a console window and print the following message:
The function of this workflow is adding two InArgument
Numbers and assigning the result to an OutArgument
Result.
AutoResetEvent syncEvent = new AutoResetEvent(false);
As the workflow thread runs simultaneously with the caller thread, the caller thread may terminate before the workflow thread. To prevent this unexpected program quit, we need to use AutoResetEvent
to synchronize caller and workflow thread.
syncEvent.WaitOne();
The caller thread will wait there, until syncEvent
is set.
wfApp.Completed = delegate(WorkflowApplicationCompletedEventArgs e) { output = e.Outputs; syncEvent.Set(); };
When the workflow completes, syncEvent.Set()
is invoked. After that, the caller can continue running to its end.
Another thing we should be aware of is how we get the result when the workflow ends. Unlike the WorkflowInvoker.Invoker
method, in a WorkflowApplication-style caller, we get dictionary output from WorkflowApplicationCompletedEventArgs
's Outputs
property; see the preceding code snippet.
- Entity Framework Tutorial
- 中文版SolidWorks 2015技術大全
- Flash CC從入門到精通
- 零基礎學后期:Photoshop+Lightroom數碼照片處理從新手到高手
- UG NX 完全實例解析
- Getting Started With Oracle SOA Suite 11g R1 – A Hands/On Tutorial
- Web 2.0 Solutions with Oracle WebCenter 11g
- 剪映短視頻剪輯與運營全攻略:視頻剪輯+音頻處理+后期特效+運營管理
- 零基礎學會聲會影2018(全視頻教學版)
- Spark Cookbook 中文版
- 人人都能玩賺AI繪畫
- Python Testing Cookbook
- 行攝 Photoshop CC后期修片高手之道(第2版)
- Illustrator CC 2018 基礎與實戰教程(全彩版)
- 中文版AutoCAD自學經典