Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
We have lots of workflow in our system.
We notice that using WorkflowInvoker.Invoke(myworkflow) was taking almost a 1 sec to execute. The workflow is a bit big, but in our test, it was doing nothing. myworkflow was build from the XAML with ActivityXamlServices.Load
Any suggestion in how to improve this?
Thanks,
Try caching the activity instance you pass to the invoker – http://www.neovolve.com/post/2010/07/23/Caching-workflow-activities-to-increase-performance.aspx