Localization of custom DLLs.

[Robert Scheer]

Hi.

I am developing a DLL that will be used by localizable applications.
The code of this DLL has some text that is send to the client
applications. I am creating some resource files for this DLL and when
I compile it, VS.NET creates a bunch of resource.dll files for the
project one for each language I need to support. So, when I distribute
this DLL to my developers, will I have to distribute those
resource.dll files as well? Is there any way to encapsulate all of
them inside a single dll?

Regards,
Robert Scheer

 

[Mihai N.]

So, when I distribute this DLL to my developers, will I have

to distribute those resource.dll files as well? Yes.

Is there any way to encapsulate all of them inside a single dll?

Nope.

Unless you invent your own solution going around the resource manager.

But having separate resource-only dlls for each language is the
current best recomended practice.

 

[Robert Scheer]

Nope.

Unless you invent your own solution going around the resource manager.

But having separate resource-only dlls for each language is the
current best recomended practice.

Hi Mihai.

So, if I support five languages, how should I deploy my DLL to my
client developers? If they need to put this DLL on the GAC, they will
have to run GACUtil.exe on each resource DLL also?

TIA,
Robert Scheer

 

[Mihai N.]

So, if I support five languages, how should I deploy my DLL to my

client developers? If they need to put this DLL on the GAC, they will
have to run GACUtil.exe on each resource DLL also?

Sorry, I don't know much about GAC deployment.
But I guess you can just give it a try.