All geek questions in one place

Designer Workflow Unusably Slow. Is it homl?

I have a WF state machine that I use to handle page navigation in WPF Media Center. He received half a dozen states, each with initialization handlers and one or two EventDriven handlers.

When you first create a StateMachine workflow using the VS template, you have the option of using a code-named model or a separate code model that describes the workflow topology in a .Xoml (xml) file.

Recently, whenever I work with State Machine, Visual Studio hangs periodically for ten seconds, after which it is always restored.

Could this be a problem inherent to Xoml parsing that will disappear if I redo the state machine using the Code-behind model?

Does anyone have relevant experience with the Workflow manufacturer in any of these models?

+3
source share
2 answers

This is a well-known issue with the workflow designer in visual studio 2008. We were promised improvements in sp1 (and presumably got them, but I didn't notice anything). Offers include:

Move all types used in workflows to a different project than where workflows live.

, , , , , . . 10 10 10 . , , . , , , 10 , .

.

- ( #/vb xoml), , , , 10 , . 2-3 .

, , 780 1000 , InitializeComponent() 16000 . .

, , .. , .

: http://blogs.msdn.com/madhuponduru/archive/2008/09/30/workflow-designer-and-performance.aspx

-Oisin

+4

VS 2008 , .

WF VS 2010 ( Win 7 RC VM), , , . , , 2008 .

, , .

0

Source: https://habr.com/ru/post/1708431/

More articles:


All Articles