[wix-users] Bundle: MSI Detects Installed=00:00:00

Hoover, Jacob Jacob.Hoover at greenheck.com
Tue Mar 2 17:44:24 PST 2021


You haven't defined how you are assigning InstallProxy, but I don't think it's going to do what you think it's going to do.

https://wixtoolset.org/documentation/manual/v3/xsd/wix/msipackage.html


InstallCondition

String

A condition to evaluate before installing the package. The package will only be installed if the condition evaluates to true. If the condition evaluates to false and the bundle is being installed, repaired, or modified, the package will be uninstalled.


That being said, we would need a bit more of the logs to try to figure out your underlying issue.  A plan dump would be handy.


From: wix-users <wix-users-bounces at lists.wixtoolset.org> On Behalf Of Bryan Dam via wix-users
Sent: Tuesday, March 2, 2021 2:02 PM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Cc: Bryan Dam <bryand at recastsoftware.com>
Subject: [wix-users] Bundle: MSI Detects Installed=00:00:00

I have a bundle with a custom BA that allows the user to, among other things, select if one of the bundle's MSI packages gets installed.

The chain looks something like this:
<Chain>
<ExePackage Id="NetCore3.1" ... />
<RollbackBoundary />
<MsiPackage Id="Server" ... >
<ExePackage Id="RestartIISAppPool" ... />
<MsiPackage Id="Proxy" ... InstallCondition="InstallProxy ~= "True"" />
</Chain>

Everything works just fine except for one scenario: If InstallProxy does not equal true then the Server MSI package doesn't install correctly. In this case the Server MSI log shows "PROPERTY CHANGE: Adding Installed property. Its value is '00:00:00'" indicating that it's already installed (?). Which doesn't make any sense because this is a fresh OS where none of our tools have ever been installed. It's a VM that I revert for each test. We have a bunch of logic to make sure we only configure IIS on initial install (ie: NOT Installed). If InstallProxy is true then the Installed property doesn't exist in the server MSI log and the Server MSI properly runs our IIS configuration and everything works.

The bundle log shows that character-for-character it's calling the Server MSI the exact same way. The InstallProxy variable has nothing to do with the Server install; it's not a condition or passed to it as a variable. And yet it impacts it somehow.

This makes no sense to me. Anyone have any ideas?

Thanks,
Bryan

____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/<http://www.firegiant.com>
NOTE: This email was received from an external source. Please use caution when opening links or attachments in the message.



More information about the wix-users mailing list