This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: Suite - Brackets in EXE name
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 09, 2012
10:18 AM
Suite - Brackets in EXE name
Hello,
can someone confirm, that the suite don't starts an EXE, if his name includes brackets?
Regards
Johannes
can someone confirm, that the suite don't starts an EXE, if his name includes brackets?
Regards
Johannes
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 10, 2012
08:58 AM
I believe square brackets are used to indicate substitutions, and there isn't an escape syntax right now. As an alternative you might add a property such that things resolve to include the square brackets. E.g. if the exe you're trying to run is named abc[def]ghi.exe, you could add a property def with value [def].
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 10, 2012
09:36 AM
Thanks Michael,
I used the wrong word.
Not brackets but parentheses.
"(" or ")".
Sorry
Johannes
I used the wrong word.
Not brackets but parentheses.
"(" or ")".
Sorry
Johannes
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 10, 2012
10:17 AM
I don't see any problems with this case. I copied notepad2.exe to Fake (parens).exe, added it as a package, and it ran. I then added it to the support files, added a button with the action {Open LAUNCHME}, and added a formatted property LAUNCHME with value [SETUPSUPPORTDIR]Fake (parens).exe, and it launched there too. What case isn't working for you? Does anything show up in the /debuglog?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 11, 2012
03:41 AM
Thankyou Michael for your efforts,
it was not the name of the file, it was a problem of the associated feature.
After deleting and rebuilding of the feature, the problem occured no more.
It remains, that I don't know, what caused the problem.
Thanks
Johannes
it was not the name of the file, it was a problem of the associated feature.
After deleting and rebuilding of the feature, the problem occured no more.
It remains, that I don't know, what caused the problem.
Thanks
Johannes