P
Piotr Strycharz
Hi
I'm wondering what is the best way to design localized applications. The SDK
says I should use ResourceManager and satellite assemblies.
However, there is a severe pitfall doing this. The application is
distributed to several customers. Of course - they want customized
resources. One can like "hello", another one - "hi". I'm not going doing
this, because I would have to keep all the versions I sold. I want customer
to customize the strings itself.
Assemblies are DLL-s. So there is no way to change resources except
recompiling application. Certainly, this is not acceptable solution. First:
I don't want to distribute code to customers. Second: they do not own
VS.NET.
The other way is to use Assembly Linker (al.exe) which is (probably, did not
check) included in SDK. Even if so, it is not acceptable, too. First: one
need to install full SDK, second: there is small probability for customer
being happy using command line tool...
Currently, I've end up with separate ASCX controls for different languages.
Controls are loaded based on selected culture. Of course, there is hard work
when changing layout. I need to do this in all the controls. Well, it's not
quite stupid idea also - some strange languages have right to left
orientation - so the pages may look different for them (not just strings).
As you can see - no solution is perfect. Any clues?
Regards.
I'm wondering what is the best way to design localized applications. The SDK
says I should use ResourceManager and satellite assemblies.
However, there is a severe pitfall doing this. The application is
distributed to several customers. Of course - they want customized
resources. One can like "hello", another one - "hi". I'm not going doing
this, because I would have to keep all the versions I sold. I want customer
to customize the strings itself.
Assemblies are DLL-s. So there is no way to change resources except
recompiling application. Certainly, this is not acceptable solution. First:
I don't want to distribute code to customers. Second: they do not own
VS.NET.
The other way is to use Assembly Linker (al.exe) which is (probably, did not
check) included in SDK. Even if so, it is not acceptable, too. First: one
need to install full SDK, second: there is small probability for customer
being happy using command line tool...
Currently, I've end up with separate ASCX controls for different languages.
Controls are loaded based on selected culture. Of course, there is hard work
when changing layout. I need to do this in all the controls. Well, it's not
quite stupid idea also - some strange languages have right to left
orientation - so the pages may look different for them (not just strings).
As you can see - no solution is perfect. Any clues?
Regards.