Windows Workflow Foundation 3
workflows memory consumption
dear members,i have some questions that looks basic:first what is the difference between placing an entire code inside workflows or just calling that code.the second question is how the workflow performance/effectiveness could be enhanced.and finaly how does CLR interpret workflows.thanks,
Abssi wrote: first what is the difference between placing an entire code inside workflows or just calling that code. <?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /> With workflow you have the additional overhead of the workflow runtime and any services, like persistence or tracking, that you add. If all you are going to do is have a code activity that executes some code workflow is overkill for you. Abssi wrote: the second question is how the workflow performance/effectiveness could be enhanced. The first instance of a workflow takes a little longer because of validation but additional instances of the same type use a cached value. Abssi wrote: and finaly how does CLR interpret workflows. Not really sure what you are looking for here. A workflow is compiled into a Type to CLR it is just another type.
To use dependency properties or not
Problem in WorkflowRuntime.WorkflowCompleted event
WWF with .NET compact framework 2.0
How can I query StateMachineWorkflowInstance before the WF idles
Question about modifying a workflow
Rule Conditions against custom activities and XAML activation - how should I achieve this?
MOSS Publishing Site
WF custom persistence once again
Hands on Labs 2.2
Error in the Hands on lab 09
How do you load XOML only State Workflow in WFPad for WWFBeta 2.2 (with namespace for codebehind assembly, and activities)?
invoke sub StateMachine workflow