Page 1 of 1

multiple executable in an msi package not installed in menu and & to execute

Posted: Tue Jan 08, 2019 8:09 am
by jsira2003@yahoo.com
In my msi package that I am creating I want 3 executables from 3 different apps. Only one shows up in the windows program menu. I am wondering if there is a way to correct or adjust this? I thought that it would just add each executable as an additional menu item for the same program since it is part of the same .msi package.

Once i installed my program with the msi package and in put it under c:\program files (x86) the & no longer works to start a video or an executable. I suspect a permissions issue possibly. Do you have any ideas?

thanks,
John

Re: multiple executable in an msi package not installed in menu and & to execute

Posted: Tue Jan 08, 2019 9:48 am
by davidc
At this time the MSI builder only generates a single shortcut for the selected file. I recommend submitting a feature request here:

https://www.sapien.com/support/upload

Potentially, you could write a custom PowerShell script that creates the shortcuts and have that run as a custom action. For details about custom action, refer to the following article:

https://www.sapien.com/blog/2018/02/26/ ... i-builder/

Re: multiple executable in an msi package not installed in menu and & to execute

Posted: Tue Jan 08, 2019 10:46 am
by jsira2003@yahoo.com
Any thought about why my & would not work after being packaged and installed in c:\program files (x86) with running my videos or executables? Is there a better way to execute these actions? This did work for me prior to creating a package.

thanks,
John

Re: multiple executable in an msi package not installed in menu and & to execute

Posted: Tue Jan 08, 2019 11:09 am
by davidc
There can be a few factors involved:

1. Make sure you are including the config files.
2. Check the platform of the executables match the of PowerShell Studio's ribbon (Home->Platform).
3. Check your script. Any code to get the directory of a script might not work in a packager environment. I recommend using the Get-ScriptDirectory function (getscriptdirectory snippet), which works in scripts and in packaged executables.

Re: multiple executable in an msi package not installed in menu and & to execute

Posted: Tue Jan 08, 2019 12:07 pm
by jsira2003@yahoo.com
I did set-location c:\program files (x86) ...

I found that if I launch my app like & $(".\app.exe") it works perfectly! If I add the full path before it, it does not work. I guess and correct me if I am wrong, if i default the location to the app path, i should be able to get away with .\app.exe.

It is working great! I suspect there may be some caveats here. I am switching between set-location sqlserver: and set-location $global:installPath. The global path is the actually path where the program got installed in c:\program files (x86)... by the .msi package.

thanks perhaps I see the light at the end of the tunnel!

John

Re: multiple executable in an msi package not installed in menu and & to execute

Posted: Tue Jan 08, 2019 12:50 pm
by davidc
I'm glad to hear you are able to make some progress. Paths are a common source of contention in packaged executes and in scripts in general.