It was a mistake on my side, the project was still referecing the WiX 3.9
BootstrapperCore.dll instead of 3.10.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Re-Bug-in-3-10-0-1823-LaunchAction-Install-is-Cache-now-tp7600737p7600747.html
Sent f
In my Custom BA I noticed a weird change:
In PlanPackageBegin:
Debugging shows that myAction has the value "Cache". Seems to be an enum
bug.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bug-in-3-10-0-1823-LaunchAction-Install-is-Cache-now-
Never mind, the culpable message box was actually the one created by the BA,
in the ExecuteError method in InstallationViewModel.cs. I simply needed to
handle the error there.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-suppress-MSI-err
I'm using a custom BA to install different MSI packages with
DisplayInternalUI="no". I have tried setting the UILevel property to 2 as
well, which made no difference.
I will still see MSI error message boxes, e.g. for 1709 Errors for obsolete
packages that have no majorupgrade handling. I want to
To give some contradictory feedback:
Installing KB3000988 did not fix the error 1316 issue on my machine.
>From the log:
MSI (s) (5C:94) [10:14:49:895]: SECREPAIR: CryptAcquireContext succeeded
MSI (s) (5C:94) [10:14:49:895]: Determining source type
MSI (s) (5C:94) [10:14:49:896]: Note: 1: 2203
I encountered the same issue and ended up writing a method in my custom BA to
manually remove the BA uninstall registry items on Close if no product
feature was installed.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/User-cancels-bootstrapper-i
We need to execute another executable from the BA.dll that requires a
specific proprietary runtime. I don't believe this to be an exotic scenario,
e.g. many hardware-specific applications might need to run some kind of
utility during setup.
--
View this message in context:
http://windows-inst
Please see http://wixtoolset.org/issues/4161/
The source has a method CreatePrerequisiteBA in
src\ext\BalExtension\mba\host\host.cpp that is only called by
BootstrapperApplicationCreate and only if GetAppDomain fails for the BA.dll.
Is this the intended design? There is no way to install other pr
To expand on this issue: when we build the bootstrapper for the Net 4 Client
framework, it will not crash (but also not install the NetFx452 via the
prereq dialog, only later).
That means, a custom bootstrapper right now could not really target the Net
4.5 framework, because the prereq installer i
With WiX 3.9.901 I've been using the NetFx451Redist / NetFx452Redist method
successfully on machines with a preinstalled Net 3.5.
When dotNetFx40_Full_x86_x64.exe (4.0.30319.1) is installed though on the
same test machine, the detection fails and my custom Bootstrapper (which
targets Net FW 4.5)
Hi,
is there a solution / workaround to the issue of multiple ARP entries for
scenarios like this one yet?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Multiple-entries-in-ARP-tp7579932p7596764.html
Sent from the wix-users mailing list archive
11 matches
Mail list logo