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,
workflows memory consumption
Hot Topic
Windows Vista
- Logon using the Administrator account
- Problem with HandleExternalEvent on a web service.
- Workflow as a navigation map for websites.
- Where can I obtain A Copy Of Windows VISTA One of the betas
- Persistence & tracking in beta 2.2
- X64 Windows Vista running X86 applications
- retrieve a list of workflow instances and select one
- Unable to write to reg key
- Problems when using While activity
- Custom Service and long running Workflow
workflows memory consumption
eyal berman
< 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.
The first instance of a workflow takes a little longer because of validation but additional instances of the same type use a cached value.
Not really sure what you are looking for here. A workflow is compiled into a Type to CLR it is just another type.