Hello,
my question:
How can i generate different setups for each language with i created with pasolo.
Description:
I tranlated my c# application with pasolo to 15 languages.
Passolo created 15 folders in each case with one translation dll.
To keep the setup small, i want to generate for each language one setup.
Are there workings available to automate something like my problem.
M.f.G Stefan
Question about multilingual applications
-
mengeleStefan
- Posts: 2
- Joined: Fri Aug 10, 2007 4:04 am
-
CandiceJones
- Posts: 904
- Joined: Thu Dec 22, 2005 7:03 pm
- Contact:
-
mengeleStefan
- Posts: 2
- Joined: Fri Aug 10, 2007 4:04 am
The language from each setup should be always english, thats no problem.
f.e.
setup_de.exe
-> programm.exe
-> language_de.dll (german)
setup_en.exe
-> programm.exe
-> language_en.dll (english)
setup_pl.exe
-> programm.exe
-> language_pl.dll (polish)
The programm.exe ist always the same but the tranlsation dlls are always different. I don't want manage 15 installaware setup project for 15 different languages of MY application and i cannot include all tranlation DLL's in one Setup.
I want to create one Installaware Project who creates 15 different setup.exe wich each includes only on translation DLL.
Sorry about my grammar
f.e.
setup_de.exe
-> programm.exe
-> language_de.dll (german)
setup_en.exe
-> programm.exe
-> language_en.dll (english)
setup_pl.exe
-> programm.exe
-> language_pl.dll (polish)
The programm.exe ist always the same but the tranlsation dlls are always different. I don't want manage 15 installaware setup project for 15 different languages of MY application and i cannot include all tranlation DLL's in one Setup.
I want to create one Installaware Project who creates 15 different setup.exe wich each includes only on translation DLL.
Sorry about my grammar
-
CandiceJones
- Posts: 904
- Joined: Thu Dec 22, 2005 7:03 pm
- Contact:
Stefan,mengeleStefan wrote: I want to create one Installaware Project who creates 15 different setup.exe wich each includes only on translation DLL.
you can use compiler variables to define the path and name of your translation dll. In the same way you can use a compiler variable to set the output name of your setup.
Then use the command line build tool where you can set the compiler variables as parameters.

