GrahamMendick

May 18, 2013 - Navigation for ASP.NET Web Forms: 08eb66147b9a, Allowed markup to include current data only, e.g., {NavigationData &} or {NavigationLink Action,&}

May 13, 2013 - Navigation for ASP.NET Web Forms: 693e81c5fdc2, Allowed a custom StateRouteHandler to be provided. Enables a different file naming structure to be used, e.g., aPage_Mobile.aspx instead of the default aPage.Mobile.aspx. In particular, gears it up for use with Glimpse, i.e., the StateRouteHandler can be wrapped making the DisplayInfo available to a Glimpse plugin

April 28, 2013 - Navigation for ASP.NET Web Forms: 09cb4b2a44b5, Removed the href rendering from the Adapter and left it up to the Interceptor so it behaves like a RefreshLink if the Adapter isn't registered

April 17, 2013 - Navigation for ASP.NET Web Forms: f9a970e7ffee, Replaced StringComparer InvariantCultureIgnoreCase with OrdinalIgnoreCase

April 16, 2013 - Navigation for ASP.NET Web Forms: efad13026bf5, Added ability to include current data in NavigationData markup by prefixing with &, e.g., {NavigationData &key1=value1} (can already pick out pieces of current data by specifying a key without a value {NavigationData key1})

April 11, 2013 - Navigation for ASP.NET Web Forms: adbeeee7d0c4, It's important that refresh navigation behaves the same regardless of whether or not it's a post back. So made the following changes to ensure that derived data is the same in both scenarios: 1. If it's not a post back then assume that derived data would be calculated, so need to retain derived data when it is a post back. This caters for when derived data is not recalculated on post back but works equally well when it is recalculated since this will happen after the post back event 2. If it's not a post back then derived data can't be passed, so if it is a post back then need to restore derived data after the ToData is processed, ensuring any derived data values in the ToData are ignored

April 11, 2013 - Navigation for ASP.NET Web Forms: 691df7968511, Added refresh navigation to a HyperLink control using markup, e.g., NavigateUrl={RefreshPostBack key=value}. HyperLink control adapter handles the Url and onclick processing. Used an event argument for post back event to distinguish from one originating from the HyperLink, in particular the one raised by a NavigationHyperLink when it's doing its own refresh post back

April 6, 2013 - Navigation for ASP.NET Web Forms: e5856e2983ac, Specifying ToData in NavigationData markup didn't work when ViewState was disabled for a Refresh PostBack because it was only set in PageComplete (PreRender or SaveState). Needed to be set ToData before the RaisePostBackEvent of the NavigationHyperLink was called. Adding a listener to the NavigationHyperLink Load Event would have resulted in more calls than necessary because only want to parse the NavigationData markup when the PostBack happens. So added a PreNavigationDataChange event to the NavigationHyperLink for the ControlBuilderInterceptor to listen to.

April 6, 2013 - Navigation for ASP.NET Web Forms: 737fd11b6813, Made NavigationData currentDataKeys constructor public so that it matches the includeCurrentData constructor, and added associated unit tests

April 4, 2013 - Navigation for ASP.NET Web Forms: 68f9ebf0a2a8, Added current data keys to both NavigationData markup and NavigationHyperLink so a subset of StateContext Data can be passed during a navigation. Useful for SPA/Refresh navigation scenarios where only specific items of current data should be retained