I am trying to come up with idea how to implement msdn like localization based on address string

```
http://msdn.microsoft.com/en-us/library/system.string.aspx
http://msdn.microsoft.com/ru-ru/library/system.string.aspx

```

I tried to find various information about ASP.NET localization, but failed to find a description of strategy that can be used to get above result.

I am not very experienced with ASP.NET and would like to get some advice on how to implement something that will result in similar paths on my website(using best possible way with least code duplication for example).

I understand that I could duplicate both files in 2 folders. or 10 files in 10 folders if i got 10 cultures. But that sounds like not the best strategy. Is there some rewrite & parameter pass going on behind or ?

**Update:** I ended up implementing it the following way: 
for my localizable pages I register routes to all current cultures ( in a generic method),
for example for `help.aspx` I register `ru-ru/help/` and `en-us/help/` routes, inside help.aspx (and other localizable pages, oop way) I analyze address string and retrieve desired language. After that I setup html contents matching the related culture provided in url.