WF can also be used to control the flow of application execution. In this technique, the view model uses WF-based workflows to control the flow of application. This delegation results in better separation of concern by keeping the view model code more maintainable and testable. The following diagram uses workflow directly. It is preferable to introduce a service layer here between the view model and workflow. This would keep us from being over dependent on the Workflow technology. This also improves unit testability.
The latest platform update of .NET Framework 4.0 has included some features based on high public demand. State machine based workflow is one of them. In this section, we would use state machines to manage the flow of our views. It can even extend to control the flow of the whole application.
When we move to MVVM, we take many things out of view to view model. This includes the flow of application. The controls on the view just take user input...
