How do I get the version into a shortcut?

[JohnO]

I want to get the Title and Version into the 'launch' shortcuts.
My first mistake was to define them in the Create Shortcut panel using $TITLE$ and $VERSION$. Neither were resolved. Then I noticed that the pre-defined one for Uninstall used #TITLE#. On this basis I redefined the Link name as: #TITLE# and #VERSION#.
Now 'title' resolves correctly, but 'version' is left as defined.
Regards, John

[FrancescoT]

Dear John,

if you have a look at IA documentation for the "Create Shortcut" command, you will find that the "Link Name" parameter has the following notes;
"The name of the shortcut as it will appear on screen. With the Windows Installer engine, no variables are allowed in this field. With the Native Engine, variables are allowed in this field."

Using the Windows Installer Engine, the "Link Name" parameter can't be resolved at runtime and due of this Variables can't be used.

However, you can use COMPILER VARIABLES with the parameter but you must define a custom compiler variable to resolve the VERSION value.

I may suggest to have a look at the sample available with the following link, that demonstrates how to set TITLE & VERSION variables using compiler variables;
http://www.installaware.com/forum/viewtopic.php?f=2&t=8927&start=0&hilit=compiler+variable

Regards

[JohnO]

Thanks Francesco
I apologise for not thinking to press F1 until I was on my train home! I discovered the info about needing to use the Native installer. The help say that I should define 'Set NATIVE_ENGINE to TRUE' in the MSI code. However, it doesn't say where in the MSI code. Editing MSI code means that I am trying to run when I can barely walk. I have tried it as the first line (after the comment) in "my project's" MSI, and in the DEFINE REGION block (pure guesswork on my part). However, the generated install code still had the Windows installer.

Where should I define the use of the native engine?
Meanwhile, I will follow your link.

Regards, John

[FrancescoT]

Dear John,

you can switch ON the NATIVE ENGINE anywhere in your code ... this depends on when you need to activate it or if you want to use it to completely replace the default Windows Installer Engine.

Because there are important differences among the engines, I may suggest you to have a look at the IA documentation about the argument.

Regards

[JohnO]

Francesco
I did have a quick look, but of course you may suggest that I look at the documentation more fully (AKA, RTFM)

John