After reading the blog entry by Ben Foster which is referenced in other items in this forum
(http://blogs.planetcloud.co.uk/mygreatdiscovery/post/Using-routing-in-a-web-forms-application-(nopCommerce).aspx)
I have attempted to implement these changes. The first steps I have attempted to go through are:
(1) The turning off of the UrlRewriting functionality by commenting out all entries related to it in the web.config file.
(2) Turning on Url Routing using code from another web site where Url Routing is presently working properly.
(3) Adding additional items to the "RegisterRoutes" procedure code to ignore .axd's and favicon's using the code from Ben Foster's blog entry regarding these two items.
Please bear in mind that Url Routing is working just fine on this same VS2010/Windows7 Ultimte/64bit machine in another web site and that code was simply moved across for initial testing purposes.
The results of this work and testing are:
(1) In procedural code on .aspx pages, the RouteTable.Routes.GetVirtualPath(...) commands appear to be working as expected and desired. The Url's created from these commands are correct and match those in the other web site where the Url Routing code came from.
(2) It would appear that none of the Url Routing is working going back into the server. In other words, if there is a
"NavigateUrl" link on one of the site pages (such as Default.aspx) and I click on that link, I am redirected to Login.aspx (of course, I am already logged in at this point). If I completel another login, I am redirected back to the Login.aspx page again. This loop will continue infinitely regardless of how many times I log in. None of the login logic was changed during these mod's at all.
It would appear that the introduction of the Url Routing table code into the global.asax file has, in some way, affected the ability of nopCommerce to know what is going on.
It should be noted that this testing was done multiple times with both possible settings for the "Enable Url Rewriting" checkbox in the Administrative section of the system. This checkbox appears to not have any effect on the process.
If anyone knows where the "hook" is, or the code that still needs modification is, or has some ideas of how to resolve this strange behavior, please give me a shout. I'm guessing that the Url Routing is not being executed on message input and that the system is "defaulting" to the login page because it doesn't know where else to send the user, but I have no idea where to look.
Thanks in advance!
Lynn