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: How to run Installshield 2016 with powershell parameters?
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
‎Apr 17, 2018
01:00 PM
How to run Installshield 2016 with powershell parameters?
I'm trying to use Installshield and run a Powershell command with parameters. I didn't find anything online or in the manual. Anyone have any ideas?
(10) Replies
‎Apr 19, 2018
12:48 AM
jweiss wrote:
I'm trying to use Installshield and run a Powershell command with parameters. I didn't find anything online or in the manual. Anyone have any ideas?
Do you mean, as a custom action?
http://helpnet.installshield.com/installshield19helplib/helplibrary/CAPowerShell.htm
Or as a *.prq?
(Just run it with params like you would from the command line)
Or are you trying to use the InstallShield Automation layer?
https://blogs.flexera.com/installtalk/2011/01/getting-started-with-installshield-automation-and-powershell/
‎Apr 19, 2018
08:42 AM
I'm trying to run it as a custom action. I right click on Custom Actions and select - New Powershell- stored in binary table.
I can do this and point to the powershell script but adding any command line options after the filename causes a error 'The file name specified does not exist.'
Is there another way to do it?
I can do this and point to the powershell script but adding any command line options after the filename causes a error 'The file name specified does not exist.'
Is there another way to do it?
‎Apr 26, 2018
07:17 AM
jweiss wrote:
I'm trying to use Installshield and run a Powershell command with parameters. I didn't find anything online or in the manual. Anyone have any ideas?
One way to handle this is to first set property values in your installer and in your PowerShell script call get-property -name [Property Name]
http://helpnet.flexerasoftware.com/installshield23helplib/helplibrary/CAPowerShell.htm
DISCLAIMER: I have never run a PowerShell custom action - but have plenty of experience with other types. 🙂
‎Apr 26, 2018
10:10 AM
As you’ve discovered, one can’t pass parameters when calling a PowerShell Script File Name.
Do what Dan L. suggested and pass your needed parameters vis [PROPERTIES]
Here is a simple PowerShell .ps1 file you can try that gets a property.
It includes a MessageBox that comes up in the middle of install that can be used to debug.
Also includes a line that writes to the Installer log.
If you place this Custom Action in the User Interface sequence you can see the dialog when running in Test User Interface mode.
You can also run the script in the PowerShell ISE app. You’ll get an error when it tries the get-property and trace-info as those are InstallShield-only components but it will run and you’ll get the dialog.
##
$Value1 = get-property -name INSTALLLEVEL
[System.Reflection.Assembly]::LoadWithPartialName("System.Windows.Forms")
$Message = "INSTALLLEVEL: $Value1 "
$Title = "Property Check"
$Buttons = "OK"
$Icon = "Information"
$oReturn=[System.Windows.Forms.MessageBox]::Show($Message, $Title, $Buttons, $Icon)
trace-info -LogMessage "INSTALLLEVEL was $value1"
##
Do what Dan L. suggested and pass your needed parameters vis [PROPERTIES]
Here is a simple PowerShell .ps1 file you can try that gets a property.
It includes a MessageBox that comes up in the middle of install that can be used to debug.
Also includes a line that writes to the Installer log.
If you place this Custom Action in the User Interface sequence you can see the dialog when running in Test User Interface mode.
You can also run the script in the PowerShell ISE app. You’ll get an error when it tries the get-property and trace-info as those are InstallShield-only components but it will run and you’ll get the dialog.
##
$Value1 = get-property -name INSTALLLEVEL
[System.Reflection.Assembly]::LoadWithPartialName("System.Windows.Forms")
$Message = "INSTALLLEVEL: $Value1 "
$Title = "Property Check"
$Buttons = "OK"
$Icon = "Information"
$oReturn=[System.Windows.Forms.MessageBox]::Show($Message, $Title, $Buttons, $Icon)
trace-info -LogMessage "INSTALLLEVEL was $value1"
##
‎May 22, 2019
02:59 AM
I use the same method.
‎Nov 24, 2018
04:48 AM
InstallShield uses setup.exe as the bootstrap loader to call the Microsoft Windows Installer service. Setup.exe can accept command-line parameters that allow you to perform administrative installations, run silent installations, and complete other administrative tasks fill kroger survey form.
‎Dec 18, 2018
01:04 PM
the filename causes a error 'The file name specified does not exist.' kroger survey
‎Dec 24, 2018
05:23 AM
The bootstrap loader is stored in the master boot record (MBR) on the computer's hard drive. When the computer is turned on or restarted, it first performs the power-on self-test, also known as POST. If the POST is successful and no issues are found, the bootstrap loader will load the operating system for the computer into memory. The computer will then be able to quickly access, load, and run the operating system.
mysubwaycard
mygiftcardsite
mysubwaycard
mygiftcardsite
‎Dec 29, 2018
06:18 AM
‎Dec 29, 2018
06:25 AM
InstallShield is a proprietary software tool for creating installers or software packages. InstallShield is primarily used for installing software for Microsoft Windows desktop and server platforms, though it can also be used to manage software applications and packages on a variety of handheld and mobile devices.
mcdvoice
mcdvoice