Shortcut name with pseudo formatting problem - Advanced Installer Community

We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

thanasis0
Posts: 4
Joined: Tue Feb 24, 2009 10:55 am

Shortcut name with pseudo formatting problem

Hi

I'm new to Advanced Installer (I've purchased AI Enterprise edition just yesterday) and I have a problem with a shortcut name with pseudo formatting e.g. [|MyShortcutName] based on a property that has a different value for each build (I have two media builds).

At first MyShortcutName property has a single word value and everything was OK but when I've changed the value to two words (with a space in between) I take an error on msi building "Exception - Reason: Invalid MSI Filename string [Word1 Word2]" where 'Word1 Word2' is the value of MyShortcutName property. After that even if I remove the space or change the name to something else that begins with the name of my company (?!) the "Edit property" dialog does not accept the value with an error message "Exception - Property value "xxxxxxxxxxx" is disallowed. Reason: Invalid internal name. Referred from: Shortcut ESProductName_test"

What I've missed? Can anyone help me please?
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Shortcut name with pseudo formatting problem

Hi,

Thank you for registering Advanced Installer.
I'm not sure why you are encountering this behavior. Can you please send us the AIP (project) file with the problem to support at advancedinstaller dot com so we can investigate it.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
thanasis0
Posts: 4
Joined: Tue Feb 24, 2009 10:55 am

Re: Shortcut name with pseudo formatting problem

Hi

I found a workaround for this problem. The trick is to set the default value of the property to a large (>8 letters) word before the use of this property as the name of any shortcut. Then (I believe) that AI makes a different short filename for the shortcut than the specific value of this property for every build.

In my case that I don't care for the default value of the property since I have a specific value for every build, I had set "x" as default value and then AI confused (I think) about the short name of the shortcut.

I think now you can reproduce it. If you don't, I can send you a very small aip sample that illustrates this glitch.
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Shortcut name with pseudo formatting problem

Hi,

Unfortunately we cannot reproduce the behavior you are encountering. Can you please send us a sample project which shows this problem to support at advancedinstaller dot com so we can investigate it?

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Shortcut name with pseudo formatting problem

Hi,

When the build process starts, Advanced Installer corrects and validates the shortcut name (it makes sure that a valid shortname is used). If the name of the shortcut has less than 8 letters, Advanced Installer will automatically add more characters to obtain a correct shortname.

However, for multiple builds Advanced Installer cannot correct (add characters to) the shortcut name. This means that the name provided for the shortcut will be used during the build process without being corrected.

For an installer property with per-build values, the default value will be used for validation. But this value cannot be corrected because of the multiple builds, so an incorrect value will end up in the shortcut name.

In this case the solution is to make sure that the default value of the property is correct from the start (it has more than 8 characters).

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”