Hosting the Workflow Designer is so much easier in .NET4 – a boon for the ISV community!

One of the most appreciated features of .NET Framework 4/Windows Workflow Foundation namespaces  is the ability to (re)host the Workflow Designer within a line-of-business design ‘surface’ (application) with relative ease. This is especially important for ISVs that prefer to provide a domain specific Workflow authoring application instead of the Visual Studio environment - the default platform for the Workflow Designer. Of course nothing wrong with using Visual Studio if you are a developer; however imagine a supply chain engineer or a auto parts purchase manager designing or monitoring a Workflow via Visual Studio, a total non-starter. While you could ‘technically’ host the .NET3.n Workflow Designer; it was not vigorously pursued due to the complexity involved and limited feature set exposed by the Designer when hosted outside of Visual Studio.

This feature alone has excited the .NET Workflow user community and has received rave reviews and actually endeared the Workflow technology to the ISV community especially those with tight budgets and daunting project deadlines. A couple of interesting quotes are posted below.

WF 4.0 Designer Rehosting: we’ve see the light!! If you’ve done projects with WF 3.5 and you’ve tryed to make in production the Designer Rehosting feature, you can understand what I mean: in WF 3.5 hosting the Workflow Designer inside an application (a WPF application for example) is too hard, not so flexible and not so intuitive for the end user. WF team has made it much easier to rehost the designer. Using XAML for WF 4.0 has made it possible to rehost the designer on a WPF form using about three lines of code. This makes is possible to construct your custom designer in Expression; which looks pretty snazzy compared to the rehosted designers of 3.x. Read more here.

Rehosting the Workflow Designer in WF4 With Windows Workflow Foundation 4 live has become much better on the rehosting front  In fact it is possible to create the fully functional and useful workflow editor below in about 200 lines of code. Now that is more like it! Read more here.

Our team is in working on a series of blog posts relating to hosting the Workflow Designer, especially focused around the specific needs of the ISV community. We expect to publish these over the next few weeks. Meanwhile do learn and acquaint yourself about hosting Workflows. Additional literature on Workflow hosting is listed below.


Comments (3)
  1. josheinstein says:

    Cool! Guess that means you also fixed the whole duplicate DependencyObject/DependenyProperty mess? 🙂

    I remember trying to host the WF designer in an application and it was basically one of the reasons (definitely not the primary reason) that we decided to abandon WF altogether.

    I am really looking forward to WF 4. WF 3 had so much promise but it was death by a thousand cuts.

  2. ValeryM says:


    Thank you for checking.

    There are no DependencyObject and DependencyProperties in WF4. So no problems! Go ahead and give hosting the WF Designer a spin. I think you will like it.

    Do review the other blog posts and let us know if you find them useful. Are there any other topics around .NET4 WF or AppFabric you would like us to discuss?

    Thank you.

  3. T Rex says:

    Hi Guys

    Ive just worked through the example on MSDN and at least there is somethign to work with but it is a little disapointing as its not easy to display built-in activities with icons, I would have expected this to be a exposed nicely somewhere so I dont need to go and reflect on assemblies and grovel around for images.

Comments are closed.

Skip to main content