I have been trying to use the Workfow Designer Control (WDC) for a few
days now and have some basic questions about Microsoft's plans for the
WDC in future releases of the Workflow foundation.
The WDC seems to have a lot of unimplemented areas in its current
state. For example the Toolbox portion of the control does not
even use the AddToolboxItem methods of the IToolboxService
interface. In fact, it looks like the actual implementation is
engineered to go around many of these features.
For sample code in a beta release, this is perfectly acceptable and I
would expect nothing else. But in order for us (the developer
community) to fully leverage the ability to use this control it really
needs to be a Release-to-Market item. Much of the actual value of
Workflows can not be realized until we are able to move workflow
authoring down to the end-user.
Are there plans at Mircosoft to fully embrace runtime workflow authoring and how will the WDC figure into these plans
What are the future plans for Workflow Designer Control at Microsoft
Hot Topic
- Error adding a custom activity to a workflow
- Roles and WWF
- Confused on why is is possible to drop activities in .XOML and .XOML.CS files?
- want to get my hands dirty
- WWF Beta 1 cleanup tool ?
- Behaviour of existing instances in updated workflow
- Timeline, It is driving me crazy.T.T;;;;;
- Missing Commit
- Passing data between activity & flow
- Statemashine workflow - Set State
Windows Vista
- Designer wish list?
- Reloading the state machine instance from persistence in Tracking
- Validation Fails on Build
- How to play a video in Direct3D
- Problem persistence status and state
- WWF Performance
- ExpenseReport Example Problem
- Microsoft Windows User Experience: Official Guidelines for User Interface Developers and Designers
- Deserialization in while loop
- ICredentialProvider
What are the future plans for Workflow Designer Control at Microsoft
Jhary
Workflow Designer Control sample demonstrates ways in which the designer can be rehosted outside the visual studio environment. It is in no way a fully functional host app for the workflow designer control and hence you see the issues such as one mentioned about toolbox above. The sample is supposed to be used as a baseline to build more richer host apps. We expect that based on specific requirements users would rehost the designer outside VS and features such as toolbox integration is part of host app.
Mark Ipoeng
Aditya,
We are also very interested in beta 2 of your sample app where you embedded the designer in a C# app.
manojnaik
Aditya,
Is there any way to get a beta 2 version of your technology sample located at http://www.windowsworkflow.net/default.aspx tabindex=4&tabid=41
kmtracker
The Beta 2 version of this sample is now available as Lab 10 in the Beta 2 WF Hands on Labs. Download at http://msdn.microsoft.com/workflow
Cheers,
Paul