How many times I’ve written about Workflow Designer Rehosting feature inside Windows Workflow Foundation? Too many times I think…
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.
I’ve received many answer from the WF Dev Team in the past about this topic and they said me that the things will change with the new WF 4.0 platform. And now?
This is the first answer…
When I’ve read this post, I was so excited… finally we can host the Designer with few lines of code and it seems more intuitive for the end user. I love the new WorkflowDesigner.Load method, were we can pass the entire WF graph to load (and it could come also from XAML or DB).
Interesting to see what will be possible when editing the loaded workflow now… if it will be easy and intuitive for the end user, this could really be a killer application!!