Thanks for the hint Nick. Here is my torch cmdline :
%WIX%\torch -ax %PATCH_ADMIN_INSTALL% -p -xo
%BASE_ADMIN_INSTALL%\setup%BASE%.msi %PATCH_ADMIN_INSTALL%\setup.msi -out
%PATCHDIR%\diff.wixmst
I tried both -ext UtilExtension and -ext
-ext %WIX%\WixUtilExtension.dll
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/XmlFile-or-XmlConfig-in-patch-msp-tp7598517p7598615.html
Sent from the wix-users mailing list archive at Nabble.com.
Does /-ext WixUtilExtension/ work?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/XmlFile-or-XmlConfig-in-patch-msp-tp7598517p7598616.html
Sent from the wix-users mailing list archive at Nabble.com.
I tried this, and also '-ext %WIX%\WixUtilExtension.dll', and while
torch/pyro didn't complain, I also didn't see an XmlFile table added by the
.msp. The XML file was not modified when I ran the resulting patch, though
the log did indicate that the enclosing component was installed.
Same result
What do your calls to torch.exe and pryo.exe look like? Do they include the
-ext flag for the UtilExtension?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/XmlFile-or-XmlConfig-in-patch-msp-tp7598517p7598549.html
Sent from the wix-users mailing
Hi all -- we are using Wix 3.8 in both our released product and service pack
1, created via torch/pyro as a .msp. We need to be able to conditionally
modify an XML file installed with the released product.
I was able to get the patch bootstrapper to show a couple of radiobuttons
using a custom
6 matches
Mail list logo
