Any thoughts on these issues?Alexander Riedel wrote:
MSI INSTALLDIR as custom action argument parameter value
Forum rules
DO NOT POST LICENSE NUMBERS, ACTIVATION KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.
Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
DO NOT POST LICENSE NUMBERS, ACTIVATION KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.
Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
- funkymonkey
- Posts: 9
- Last visit: Wed Jan 11, 2023 8:57 am
Re: MSI INSTALLDIR as custom action argument parameter value
- Alexander Riedel
- Posts: 8488
- Last visit: Tue Apr 16, 2024 8:42 am
- Been upvoted: 37 times
Re: MSI INSTALLDIR as custom action argument parameter value
There is a lot to answer here. I would still recommend to read up on the Windows Installer and WiX toolset documentation.
- The installer error your are getting is because the version number was not increased between builds. As the error message says, it will not install the same version that is already installed.
- I have no idea why the quotes on parameters are there. I have handed that issue to QA to investigate.
- The PowerShell V5 required message when uninstall is invoked from the dialog is a known WiX Toolset issue. It evaluates the property but not the registry search preceding it.
As the check for PowerShell 3,4 and 5 will disappear soon anyway, I would recommend to simply not use that. PowerShell 5.1 has been part of Windows for some time now,
there really is no longer a need checking for it.
- To run a custom action silently, I would probably just package its as a silent exe. WiX will run a console application (like pwsh.exe or powershell.exe) with a ... console.
I am sorry, but we cannot take feature requests for Windows Installer or the Wix toolset.
- The repair option is generally disabled for installers generated with our tool. For the sake of simplicity mostly, as that would require another option somewhere.
The installers generated for PowerShell script, modules or applications generally are not large enough that a repair can beat an uninstall / reinstall timewise.
- The installer error your are getting is because the version number was not increased between builds. As the error message says, it will not install the same version that is already installed.
- I have no idea why the quotes on parameters are there. I have handed that issue to QA to investigate.
- The PowerShell V5 required message when uninstall is invoked from the dialog is a known WiX Toolset issue. It evaluates the property but not the registry search preceding it.
As the check for PowerShell 3,4 and 5 will disappear soon anyway, I would recommend to simply not use that. PowerShell 5.1 has been part of Windows for some time now,
there really is no longer a need checking for it.
- To run a custom action silently, I would probably just package its as a silent exe. WiX will run a console application (like pwsh.exe or powershell.exe) with a ... console.
I am sorry, but we cannot take feature requests for Windows Installer or the Wix toolset.
- The repair option is generally disabled for installers generated with our tool. For the sake of simplicity mostly, as that would require another option somewhere.
The installers generated for PowerShell script, modules or applications generally are not large enough that a repair can beat an uninstall / reinstall timewise.
Alexander Riedel
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.