InstallAware

Hello,
I understand that InstallAware replaces double backslashes with single ones \\ =>
Can I avoid this behavior?

I have a problem with the Run Program action which should run $TARGETDIR$\postinstaller.exe with command line parameters such as
/install="$TARGETDIR$\config.dll"

When $TARGETDIR$ contains a UNC path (starts with \\ ), the Run Program action can execute the file, but the $TARGETDIR$ variable in the command line parameters is changed, and thus the path in the command line parameters is invalid.

Dear Rasmusw,

just try to add an additional backslashes to your parameter argument, when the argument variable contains an UNC path (starts with \\ ).

Example;

The same as IA clipboard format;

With the above code I used "cmd.exe /k ECHO ON", for the sole purpose to print out the effective argument value passed out by "Run Program".

Hope this helps you.

Regards.

Hello Francesco,
thank you for your suggestion, I will try it.

Best regards,
Rasmus

It should work ... I used the same with a project.

Regards

Has this been improved in the latest releases, e.g. X17, to turn off the behavior? It's a pain to anticipate this all over an installer and apply workarounds.

Also, the behavior is very annoying when the user tries to actually type double-backslashes.

This topic applies to InstallAware Multi Platform as well.

Each programming language has its own escape sequence for particular characters, this is simply how it works for InstallAware.

I'm not necessarily talking about the programming language, but the auto-replacement of the double-backslash in the edit box, as the user types in.

Can that actually be explained by the data flow as the user types, say back and forth from the UI into the variables, and thus the replacement happens?

In any case, you can imagine how annoying this can be for the end user, typing one thing and seeing another. At one point, the cursor even jumps back to the beginning of the string, and typing more backslashes doesn't do anything.

Oh, most interesting!

Please provide a minimum reproducing project for further research and escalation.

JohnGaver wrote:Please provide a minimum reproducing project for further research and escalation.

Simply create a new project in X17 and "bind" a user variable to an edit box using the "[Written variable value]" option. The other options there seem fine, like the “Installation Folder“, but are not appropriate for the task at hand.

I'm guessing that the behavior is intentional, but there's a need for a generic option that will allow any input, w/out parsing for escapes.