.net - WF4 Sequence vs Flowchart -



.net - WF4 Sequence vs Flowchart -

from initial experimentation wf4, appears flowchart can represent workflow as sequence flow, although reverse not true. if right (and forgive me if i've missed something), there advantage @ ever using sequence workflow?

from can tell, preferable start flowchart model offers more flexibility future remodelling if required. if start sequence, you're never going add together flowchart-style branching/decisioning.

does sound sensible approach take?

no doesn't.

for 1 flowchart flexible doesn't straight back upwards lots of capabilities pick or parallel structure. , flexibility comes price, more work create simple sequence if steps. , quite mutual appearance.

basically saying c# produces msil can in c# can done in msil not can in msil can done in c# should programme in msil only.

in fact wf4 model makes real easy combine different styles. can start sequence, embed flowchart, embed sequence , state machine in there. far runtime , designer concerned activities.

.net design workflow-foundation-4

Comments

Popular posts from this blog

iphone - Dismissing a UIAlertView -

c# - Can ProtoBuf-Net deserialize to a flat class? -

javascript - Change element in each JQuery tab to dynamically generated colors -