1
Vote

PageFlow does not allow NavigationService to be customized; value is hardcoded to Microsoft.Practices.PageFlow.Services.NavigationService

description

I originally suggested this change before the PageFlow block was broken out of the WCSF core; it remains a suggestion that should be implemented. A custom navigation service is necessary to use PageFlow outside of a simple set of ASPX pages (I have successfully used a custom navigation service to implement PageFlow both in a ASCX state machine and within the DotNetNuke framework). Please consider it for a future release!
 
Specific discussion on changes necessary to implement this enhancement is located here: http://www.codeplex.com/websf/WorkItem/View.aspx?WorkItemId=15208.
 
I write about WCSFContrib-specific modifications here (I do not believe much, if anything, has changed with respect to modifications since PageFlow was moved to its own project): http://brandonhaynes.org/gameplan3/brandonblog/Home/tabid/489/EntryID/11/Default.aspx

file attachments

comments