Rehosting WWF designer

Related Hosting workflow designers In MS-help: // Ms. mssdk.1033/ms. netfx30sdk. 1033/wf_gettingstarted/html/185cc192-b19d -463c -80 dB -6c 2d488419e7.htm Has the following content:

The primary classes that you must use when you host a workflow designer are as follows:

·The. NET designsurface class, which implements what the user perceives as a designer by providing a completely self-contained design surface.

·The workflowview class, which displays a visual representation of a workflow that is described in workflow markup.

·The workflowdesignerloader class, which supports custom loading of a workflow designer and workflow designer components.

·The workflowdesignermessagefilter class, which creates message filters to respond to workflow designer events, such as drag operations, layout and paint operations, and other designer events.

An example is provided.Basic designer hosting. We can loadSequentialWorkflowOf course, this example is very simple.This is also cited and translated by many people. Based on my verification during the development and testing process, I would like to elaborate on myHosting workflow designers.

Designsurface: An Important class that is supported during design, although the name containsSurfaceA word, but it cannot be displayed. He focuses on adding and obtaining services. These services include toolbox, menu, host during design, type description, and selection.

Workflowview: This class is not likeWindows SDK documentationAs mentioned above, itNot required. What we are talking about here is not mandatory, it means we don't need to display it."New"If you do not need to filter messages, you can even connect them."Workflowview"This class name is not required. InDesignsurfaceThere isViewAttribute, which is the visual interface of our designer. We just need to put it on our own container.

Workflowdesignerloader: Without it, we can display the designer and useCodeDesign the content in the designer. But if you wantWorkflowThe designer must be used to directly respond to users' mouse and keyboard events. And if you want to make the design things persistent, you 'd better do it here.

Workflowdesignermessagefilter: If you wantDisableUser pairWorkflowThis class can be used for some Interaction Events of the designer or for some special things; and this class isWorkflowdesignerloaderIt can be used together, otherwise it will not work. In other words, we usually don't care about this class. This class is optional rather than necessary.

if you want to make a designer like vs integrated environment, you still have a lot to do. Such as toolbox and attribute window. There are still a lot of technical points here, especially the support for dragging the mouse from the toolbox to the designer, which gave me a lot of detours, but it was finally implemented. If you are busy at work, wait until I have time to write it again.
for the Article about rehosting WWF designer, see my other articles:
some technical details and application experiences of WWF (I)
some technical details and application experiences of WWF (II)
Custom activity appearance during running of rehosting WWF designer
Custom activity exterior of rehosting WWF designer
drag activity from toolbox to designer
rehosting WWF designer