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: BASIC-MSI: Powershell Custom Action
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
‎Jun 12, 2015
06:31 AM
BASIC-MSI: Powershell Custom Action
Hello,
I am testing the new CA Powershell interface.
The PS1 looks like:
$Value = get-property -name PROP1
set-property -name PROP2 -value $Value
trace-info -LogMessage "I am a PowerShell custom action "
trace-info -LogMessage $Value
The commandlet set,get property works properly. In my example PROP2 gets value of PROP1.
But I can not see in the msi log file any comment made by trace-info.
Can you check it, please?
I am testing this setup on W10-x64 (10130), setup is 32-Bit.
IS2015 works on W10, too.
Thanks.
I am testing the new CA Powershell interface.
The PS1 looks like:
$Value = get-property -name PROP1
set-property -name PROP2 -value $Value
trace-info -LogMessage "I am a PowerShell custom action "
trace-info -LogMessage $Value
The commandlet set,get property works properly. In my example PROP2 gets value of PROP1.
But I can not see in the msi log file any comment made by trace-info.
Can you check it, please?
I am testing this setup on W10-x64 (10130), setup is 32-Bit.
IS2015 works on W10, too.
Thanks.
(2) Replies
‎Jun 12, 2015
01:59 PM
The trace-info cmdlet is a thin wrapper around MsiProcessMessage and so the usual limitations apply. So for example if you are calling the custom action from a DoAction Control Event this will not work.
If this is not the case can you please provide more information about how and where the action is scheduled. Also you mentioned this was a problem on Windows 10, does this work on other versions of Windows or is 10 the only one you have test on?
If this is not the case can you please provide more information about how and where the action is scheduled. Also you mentioned this was a problem on Windows 10, does this work on other versions of Windows or is 10 the only one you have test on?