I'm currently testing various methods for localisation, I don't like the way mvc does it as it compiles the language files into the dll which means to add a new language you have to recompile the code which to me seems an enormous step backwards in terms of functionality, with a simple asp.net website the resource files are complied at runtime by the server, so you can just chuck a new resource file on the server and recycle the website and it then supports the new language.
to do the same in mvc requires writing a custom provider so you can store the language strings in either the database or xml files, so I am doing a few tests to see which is the best approach