The PageFlow Application Block, MVC4 and Visual Studio 2010

Davidsmith

New Member
I am in the process of evaluating technologies, prototyping and potentially defining application architecture for a suite of web based applications that have been written using, ASP.Net WebForms, UIP, Unity, MVP, and a custom frameworks that wraps Entlib 3.1. Some of the problems we have with the current toolkit are: [*]It is really hard to utilise the latest client-side technologies to build Progressive Enhancement into the presentation layer. [*]User Controls are inherently hard to re-use and the added complexity of producing Server Controls inhibits their use on a wide scale.[*]The master page concept does not provide an organisation-wide reuse. It needs to be customised heavily by the project teams anyway.[*]It is extremely hard to produce accessible, compliant and cross-brower compatible HTML. [*]There is little or no opportunity for having reusable screens (Views) across applications within the portfolio. One of the key requirements that we have is the ability to produce configurable/compose-able navigation flow. In the current architecture, UIP application block allows for that with relative amount of ease. We are evaluating the use of ASP.Net MVC4 for our future web applications.My question is this: Has anyone implemented UIP-style configurable / compose-able navigation capability with ASP.Net MVC? I came across the PageFlow Application Block: http://webclientguidance.codeplex.com/wikipage?title=Page Flow Application Block that is slated to solve this exact problem.I downloaded the PageFlow Application Block from the wcsf contrib project, http://wcsfcontrib.codeplex.com/, but the source code does not even compile on the VS2010. Has anyone used the PageFlow application block? Is this application block unsupported, and therefore obsolete? If you had a requirement to do configurable navigation capability for wizard style web applications, how would you do it?Sorry for the long-winded question. I wanted to provide as much context as possible.
 
Back
Top