Localized shortcuts in installer built by Team Build

ElenaN · Post by **ElenaN** » Mon Aug 03, 2009 10:18 am

I have a very strange problem
I added installation package creation to the Team Builds in TFS (BeforeDropBuild target). If I get latest files from TFS and build installer manually, it works OK. But installers which are created by team build corrupt my localized shortcuts.
Let me show what I mean under corrupted shortcuts:

Default non-unicode language Greek, installation in Greek.
Instead of:
Άδεια χρήσης
Συχνές ερωτήσεις
I got pic.1

Default non-unicode language Russian, installation in Russian:
Instead of:
Лицензионное соглашение
Часто задаваемые вопросы
I got pic.2. (shortcut names look like blank, but actually they don’t)

I don’t know what to do. I need some hint how I can find the reason of this strange behavior.

File Attached:

pics.JPG

ElenaN · Post by **ElenaN** » Tue Aug 04, 2009 5:23 am

Hi again
I’ve found the reason of the issue. Hurray!!!

It wasn’t connected to tfs at all. It is kind of a bug in InstallAware as it seems to me.

There is an“/o” parameter for building from Command Line:
miabuild.exe <projectfile> [/o=<outputfolder>] ….
/o Optional parameter, full/partial path to custom build output folder.

If partial path is provided after /o parameter (e.g. /o=”.\\output”) everything is fine.

But usage of full path (e.g. /o=”D:\\output”) leads to strange shortcut issue – for any language with has differ that English ANSI code page (not 1252) shortcut names are shown incorrectly after installation.

MichaelNesmith · Post by **MichaelNesmith** » Tue Aug 04, 2009 7:27 am

That's very interesting, but:

1) You should always use full paths. InstallAware does not support relative paths anywhere.

2) Read the #CODEPAGE# pre-defined compiler variable in help, that is probably the proper way to solve your problem.

ALive · Post by **ALive** » Tue Aug 04, 2009 9:02 am

Hi, Elena

Try to use
#CODEPAGE# = 0

This helped me to resolve the issue with squares instead of Russian letters inside the Shortcut names and Descriptions.

Hope this helps!

ElenaN · Post by **ElenaN** » Wed Aug 05, 2009 4:51 am

WOW ALive, you are right again!!! Installers with 1252 codepage have shortcut issue, while Installers with codepage=0 don’t have it.

But strange why when I don’t specify CODEPAGE and build with different (full or partial path) in /o parameter the result msi codepage is differ….