Strategies for (embedded) Resource DLLs

The developments systems for VCL (Delphi and C++Builder) and MFC (Visual C++) have built-in support for resource DLL files. This technique gives you as developers an easy way to organize your localizations.

At startup an applications checks if the language of the system is the same as the original resources. If it differs than these systems look for resource DLLs matching the needed language.

You get this luxury system without any coding. In Sisulizer you only have to set one check box and you can use this state-of-the-art technique.

Screen Shot: Multilingual EXE or DLLs

Delphi supports various options to go international. You can compile an executable for each language, ship a multi-language exe, use resource dlls, or even embed them in your executable. No matter which way fits your needs best, Sisulizer supports them all. Single language exes, multilingual exe, resource dlls or embedded resources. Sisulizer supports all options your platform supports, here Delphi - click screen shot to enlarge

There are two disadvantages of the resource DLLs technique. First you have to distribute more than one file and second the version of the application and the DLLs must match perfectly. If a user decides to mix different versions of your resource DLLs he gets into trouble.

But it is easy to also overcome this problem. Simply embed the DLLs into the main application. In Sisulizer this is also just one mouse click away. Add some lines of code to extract the embedded DLL at start-up to your application and you have the most advanced localization technique available. An examples how to do this is installed with Sisulizer.

Download Sisulizer now and try it free for 30 days.