See http://stackoverflow.com/questions/13271048/net-4-5-mvc-routecollection-lowercaseurls-breaks-when-using-area for full details.
It appears that this is caused by there being multiple instance of RouteCollection - one "global" one, and one per area. Presumably we'd need to propagate the settings from the parent RouteCollection to the area ones (or something like that).
Comments: Hello! This is my first contribution so I hope I did not mess up to badly. :) Here is a patch file to fix this issue. The change also addresses other 'potential' issues with the properties AppendTrailingSlash and RouteExistingFiles which would suffer the same fate as LowercaseUrls when using an Area. It also includes test cases to verify the problem, as well as the fix. Best Regards, Grant
It appears that this is caused by there being multiple instance of RouteCollection - one "global" one, and one per area. Presumably we'd need to propagate the settings from the parent RouteCollection to the area ones (or something like that).
Comments: Hello! This is my first contribution so I hope I did not mess up to badly. :) Here is a patch file to fix this issue. The change also addresses other 'potential' issues with the properties AppendTrailingSlash and RouteExistingFiles which would suffer the same fate as LowercaseUrls when using an Area. It also includes test cases to verify the problem, as well as the fix. Best Regards, Grant