Your request is not really clear. The file name you posted “gerLng.dll” indicates that you are working on an C++ project localizing Win32 DLLs. It would be helpful to get some more information. There are various target file settings that can help to solve your problem.

In the end you will need some information and help from your developers as Passolo is just generating the translated DLL. Registering translated DLLs for your software is a tasks that usually takes place in your installer/setup utility.

Hello Achim

thank you for reply. yes my original english resource dll was compiled with c++, and now i want to use it with sdl passolo to translate it to different languages, but when i send it out they complain that they can not use it as it have same product id as the original english one. My question is if there is any setting, that can make the newly created, for example german.dll to be independent of the original english without inheriting it's productid.

Appreciate your help

???
That's how resource DLLs are supposed to be, AFAIK...

I've done quite some localizations using Passolo (perhaps Achim would even remember our testing of .NET plugin betaversion back in Passolo 4 ;-) ) and never ever heard about issues with ProductID...

???
That's how resource DLLs are supposed to be, AFAIK...

I've done quite some localizations using Passolo (perhaps Achim would even remember our testing of .NET plugin betaversion back in Passolo 4 ;-) ) and never ever heard about issues with ProductID...

So you're saying that all newly created (with sdl passolo) resource files for all languages should share same producID??? i have never heard about it

And why exactly would that be a problem?
They DO belong all to the same product, don't they?

sorry meant ProgID or CLSID

I'm not a developer, but... doesn't this relate to a code, not to the resources?
Passolo doesn't touch the code...