Shulou(Shulou.com)06/02 Report--

This article mainly shows you "what are the new features in WF4 Beta 2", the content is easy to understand, clear, hope to help you solve your doubts, the following let the editor lead you to study and learn "what are the new features in WF4 Beta 2"?

This article will introduce the new features in WF4 Beta 2, and through the comparison between WF4 Beta 2 and WF4 Beta 1, you can better understand WF4 Beta 2.

The Acticvity structure describes the Activity structure of WF4 Beta 2

Comparison of Activity structure changes between WF4 Beta 2 and WF4 Beta1

1. Cancel [WorkflowElement], and like WF3.0, [Activity] has become the root type of the WF function Activity

two。 Added the expression Activity [ActivityWithResult]

Public sealed class wxwinterActivityResult: CodeActivity {protected override string Execute (CodeActivityContext context) {return "wxwinter";}

3. Asynchronous Activity [AsyncCodeActivity] is added to implement the asynchronous execution mode of Begin/End.

Public sealed class wxwinterActivity: AsyncCodeActivity {protected override IAsyncResult BeginExecute (AsyncCodeActivityContext context, AsyncCallback callback, object state) {return callback.BeginInvoke (null, null, null);} protected override void EndExecute (AsyncCodeActivityContext context, IAsyncResult result) {}}

4. Cancel [InvokePowershell] Activity

For an introduction to [InvokePowershell] Activity, see my WF4.0 Beta1 call PowerShell.

(http://www.cnblogs.com/foundation/archive/2009/06/28/1512542.html)

5. Add Activity [Rethrow] to rethrow the exception

Comparison of Activity structure changes between WF4 Beta 2 and WF3.0/3.5

It has changed so much that it can basically be thought of as two products.

The running environment describes the running environment WorkflowApplication of WF4 Beta 2

Class Program {static void Main (string [] args) {WorkflowApplication instance = new WorkflowApplication (new wxwinterActivity ()); instance.Run (); System.Console.Read ();} public class wxwinterActivity: CodeActivity {protected override void Execute (CodeActivityContext context) {System.Console.WriteLine ("wxd");}}

Comparison of the running environment between WF4 Beta 2 and WF4 Beta1

The process instance [WorkflowInstance] is replaced by [WorkflowApplication]

Class Program {static void Main (string [] args) {WorkflowInstance instance = new WorkflowInstance (new wxwinterActivity ()); instance.Run (); System.Console.Read ();} public class wxwinterActivity: CodeActivity {protected override void Execute (CodeActivityContext context) {System.Console.WriteLine ("wxd");}}

Comparison of the running environment between WF4 Beta 2 and WF3.0/3.5

The most obvious change in the running environment of WF3.X and WF4 is that WorkflowRuntime's CreateWorkflow method is used to create an instance in WF3.X.

In WF4, instead of showing how to create a [WorkflowRuntime], you can create it directly using [WorkflowInstance (in Beta1)], which is why you renamed [WorkflowInstance] to [WorkflowApplication] in Beta2.

Class Program {static void Main (string [] args) {WorkflowRuntime workflowRuntime = new WorkflowRuntime (); WorkflowInstance instance = workflowRuntime.CreateWorkflow (typeof (wxwinterActivity)); instance.Start (); System.Console.Read ();}} public class wxwinterActivity: System.Workflow.ComponentModel.Activity {protected override System.Workflow.ComponentModel.ActivityExecutionStatus Execute (System.Workflow.ComponentModel.ActivityExecutionContext executionContext) {System.Console.WriteLine ("wxd"); return base.Execute (executionContext);}}

Workflow Development description Workflow template provided by WF4 Beta 2

WF4 Beta 2 only provides a template for [Activity]

When you create a process using a [Activity] template, it provides an empty environment in which only one control can be placed.

Activity >

When you put [Sequence] into an empty Activity, it can be considered a [sequential workflow].

Activity >

When you put [Flowchart] into an empty Activity, it can be considered a [Flowchart workflow].

Truex:Boolean > scg3:Dictionary > sap:WorkflowViewStateService.ViewState > Sequence > Activity >

Comparison of workflow templates provided by WF4 Beta 2 and WF4 Beta1

WF4 Beta1 clearly provides two workflow templates [Flowchart Workflow] and [Sequential Workflow]

[sequential Workflow]

[Flowchart Workflow]

Description of workflow-to-template comparison between WF4 Beta 2 and WF3.0/3.5

WF3.0/3.5 also provides two workflow templates [state machine workflow] and [sequential workflow]

Among them, [state machine workflow] is similar to [Flowchart workflow].

[state machine workflow]

[sequential Workflow]

Workflow format description

The workflow of WF4 can be built in code or xaml, and xaml can be compiled into a class dynamically / statically, or it can be loaded directly as a string

The workflow of WF3.X can be built by code or by xoml. Xoml with class header can be compiled into a class dynamically / statically, and xoml without class header can be loaded as a string directly.

Other feature description

Both WF4 and WF3.5 provide persistence, tracking, communication, blocking and other functions, but the implementation is different and not universal.

The process designers of WF4 and WF3.5 are also very different in terms of UI style and implementation.

These are all the contents of the article "what are the new features in WF4 Beta 2?" Thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to follow the industry information channel!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.