Hi!
I tried to search for proper suggestion forum, but figured out this is the best place for the topic.
I'm waiting to the control vendors to come up with proper Workflow Designer for Windows Workflow Foundation (.NET 3.0 and above).
Now that you have good lineup with next generation ASP.NET control toolkit I'd really like to see the following implemented (and I'm sure all the people out there working with workflows would as well):
1. Support for running sequential and state machine workflows as ASP.NET applications with little code directly. The workflows initially include the application logic and basically could be in generic way wrapped within a controlset that would provide the input/output connectivity.
There are already general .NET community examples available for workflows as-is as ASP.NET applications with page transitions described as state changes in state-machine workflow.
2. Workflow designer customization. For either Windows Forms or even for ASP.NET (would be superb).
The existing Visual Studio used Workflow designer is good start, however customizing its looks and behaviour could use some general best-practices control vendor touch.
I'm sure these will be added to some component vendors products within reasonable time, but I'd be darn glad to see them in yours.
Br,
Kalle Launiala
I tried to search for proper suggestion forum, but figured out this is the best place for the topic.
I'm waiting to the control vendors to come up with proper Workflow Designer for Windows Workflow Foundation (.NET 3.0 and above).
Now that you have good lineup with next generation ASP.NET control toolkit I'd really like to see the following implemented (and I'm sure all the people out there working with workflows would as well):
1. Support for running sequential and state machine workflows as ASP.NET applications with little code directly. The workflows initially include the application logic and basically could be in generic way wrapped within a controlset that would provide the input/output connectivity.
There are already general .NET community examples available for workflows as-is as ASP.NET applications with page transitions described as state changes in state-machine workflow.
2. Workflow designer customization. For either Windows Forms or even for ASP.NET (would be superb).
The existing Visual Studio used Workflow designer is good start, however customizing its looks and behaviour could use some general best-practices control vendor touch.
I'm sure these will be added to some component vendors products within reasonable time, but I'd be darn glad to see them in yours.
Br,
Kalle Launiala