While playing around with localization using Matt Hawley's approach. I wonder if someone has figured to localize routes. I can do this using global resources per site. But when I would try to make it a users choice (so users can switch between languages) the architecture does not allow it because the routes are mapped at application startup and not at session level. Do I have to provision a site per language? What am I missing?
A:
You don't need to create one site per language.
What I would try to do is use the default controller to catch all requests. Then translate the controller name + action into a base language and then redirect the route appropriately.
ajma
2009-01-30 06:48:35
+1
A:
No sure if this is what are you asking, but in this question I present a solution using asp.net routing (the same used in MVC) for dealing with routes and languages.
Eduardo Molteni
2009-04-15 23:32:08
A:
maybe this is also a help on this topic
http://haacked.com/archive/0001/01/01/internationalized-urls.aspx
silverfighter
2009-04-27 19:58:44