Search
Closed
as Postponed Help for as Postponed

1
Sign in to vote
0
Sign in to vote
Sign in
 to vote
Type: Suggestion
ID: 505288
Opened: 10/28/2009 2:50:43 PM
Access Restriction: Public
0
Workaround(s)
https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=98117
Details (expand)

Product Version
.NET Framework 4.0 (Beta 1)
Product Language
English

Operating System
Windows Server 2003
Operating System Language
English

Architecture
x86

Priority
(1=blocking, 2=important, 3=nice to have)
2

Severity
(1=major functionality issue, 2=important functionality issue, 3=nice to have)
3

Component Usage
(what aspects of the product are you using and what is the scenario you are wishing to accomplish)
Both client side and server side use of a good hiearchical state machine has many uses. For example implementing the Controler in a MVC design
Suggestion/Feedback:
(what would you like to see improved/changed in future versions/SPs)
Simply add a robust state machine to WF building on what was done before.
Capture the essence of this following this book as a guide:
http://state-machine.com/psicc2/index.htm
Proposed Solution
See suggestion/feedback. Basically a re-engineered state machine workflow.
And no, I don't see the new flowchart as a valid replacement. The key is to allow
proper nested states and have the superstates handle events not specifically handeled by substates. This give you control over complexity.
Benefits
Faster Development

Other Feedback
 
File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 10/29/2009 at 5:15 AM
Thank you for your feedback, We are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
© 2009 Microsoft Corporation. All rights reserved. Microsoft Connect Terms of Use | Trademarks | Privacy Statement