Workflow Foundation the other Way

Topics: Web Client Software Factory
Nov 14, 2006 at 1:45 PM
Currently, you use the workflow foundation to manage overall the page flow process.
I thought about, why not doing it the other way.
you go directly into an page, and the page say's, to what Workflow it is depending on.
so, the SelectPaymentMethod.aspx says, it depends on an PaymentWorkflow.
and the dependency injection now get the current payment workflow for the specific user and assigns it.

And when the component's work is finished, e.g. the payment method is choosen and validated, it calls to the workflow foundation the specific action, and the workflow deside, where to go next.

the benefit would be, that not the overall process is managed, and you can port the parts of the whole website one ofter another.

what do you think?
Nov 14, 2006 at 6:02 PM
I still getting on board of this wagon but, for me, it what makes sense is the workflow determing what the view (ASPX) is according to the current state, not the other way around.

The virtual path should point to a process (workflow or similar) and that process should make a decision on what is the current view.