In this series of articles I'll show how (in my opinion, obviously) to the Page Flow Application Block of the Web Client Software Factory could be improved.
- Removing Database Dependencies
Especially in development and demonstration scenarios, the dependency on a database can be a big hassle. In this article I'll show how to remove this dependency
- Decoupling Page Flow Usage From Its Implementation
I don't like the fact that I need to know the type of a page flow definition. Or even the fact that a page flow definition has a type. In this article I'll change the Page Flow Application Block to be possible to get page flows by its definition name instead of its definition type.
- Current Definition And Current Page Flow
There are a number of classes in the in the .NET Framework that expose a static (shared in Visual Basic) property with a reference to an instance valid in a particular scope (usually the current thread).
In this article I'll change the Page Flow Application Block
to add properties to the page flow directory in order to take advantage of the work done by the page flow provider.
Filed under: .NET, Architecture, ASP.NET, Community, SoftDev, Microsoft, MSDN, MVP, Web, WCSF, PnP, SoftwareFactories, PageFlow