Rob,
I have failed to get the to work. I think I need more time
to understand the tool's layers.
In the race for time I have done the following to at least get what is
needed to for the bootstrapper to work for now.
This way when the user canc
Thanks Rob,
will give it a go and keep informed if I manage to solve it.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-EXEPackage-Condition-does-not-get-evaluated-when-MSIPackage-Installation-is-cancelled-tp7183696p7186616.html
Sent from the
1. The InstallConditions are evaluated before any packages are executed.
Look in the bundle log file and you should be able to see the "plan" that
spells out what is going to be done to each package.
2. The Condition attribute on the Bundle element determines whether the
Bundle can be launched at
Addiditonal info:
If I try to Disable the UI for the MSIPackage, it fails since the UAC is
turned on and the prompt to key in the admin credentials are not shown. The
MSI already have the "elevated" value in its package.
--
View this message in context:
http://windows-installer-xml-wix-toolset.6
Hi All,
I have been having problems with the Burn bootstrapper when the MSIPackage is
installed with the "DisplayInternalUI=yes". We need this as a requirement.
The problem I face is that When we click on "Cancel" for the MSI installation,
the whole prerequisite is going into a reinstall or rep
5 matches
Mail list logo