During lasts weeks we've been planning the adoption of an MVC inplementation for some of our apps, I've worked with some that are commonly used [Maverick, UIPAB, CAB], but since some of our techical goals are not completely covered by any of these, we were in the need to find something more suitable, first of all and since my particular point of view, Maverick implementation is kind of weird an not practical since you have to make many set up tasks before you can use it to loosely couple your User services with your business logic, in other words ... to much effort for poor functionality, in the other hand our apps needed some kind of task persistance wich is not provided by Maverick.
Said that ... UIPAB seemed like a good option, since it is easy to implement for ASP NET apps and it also provides a persistance management mechanism for user tasks, however this implementation is not up to date (last released was for VS 2005), it seems like Microsoft Apps Blocks team abandoned this block in search for a better implemetation with MVP pattern and, as I remember the last release had some issues, especially talking about open navigator which in these case would be necesary, in that time I remember John Nelson had to develop a custom navigator to cover the graph navigator provided by UIPAB.
CAB [Composite UI App Block] is also a good option that also has support for WF, tought, at this moment it only supports implementation for windows apps and not for ASP.NET, it is planned a release of a version for ASP.NET, but in the meantime we needed a solution for ASP.NET.
In the other hand we could also consider WF to provide our app with process workflows, but in these case we see a potential risk, altough we have a working knowledge on this matter as it is a new Microsoft technology which could take us some time to implement in the app.
Searching on the web we found 'Ingenious MVC' that is the target of this post series, in the next post I'll talk about some of the caracteristics we found attractive over the implementations I already mentioned, further posts will be focused on how we develop some changes for Ingenious and implement it in a real world app to support plain vanilla workflows.
eeaa308f-566b-4349-b5a8-6c68958cfb6d|3|5.0