I found the following extract here :
http://openmymind.net/index.aspx?documentId=3
**************************************************
Why not use what's available as-is?
While it's certainly possible to develop a multilingual application
with the tools provided with ASP.Net, there are a number of limitation
which make the task less than streamlined. Some of the key problems
are:
* Resource files are embedded into [satellite] assemblies
* Resource files can't return strongly-typed objects
* Web controls aren't easily hooked with resource files
While the list might seem small, the above three issues can be quite
serious - with the first being the worst. For example, since resource
files are embedded into assemblies, its very difficult to ship a
product which provides the client with the flexibility to change the
content - a feature offered by many products. At my previous job, every
time the translation department wanted to change some text, we'd need
to recompile the entire application, stop 20 web servers and copy the
..dll into the bin folder - a frustrating process.
**************************************************
I think this last pretty much answer my question, seems one cannot add
languages on the fly, a recompilation is needed !!
Really !?