On 01-Mar-13 05:01, Tobias S wrote:
ExePackage SourceFile=c:\WinPcap_4_1_2.exe /
You need a DetectCondition; without one, Burn has no way of knowing
whether the package is already installed.
--
sig://boB
http://joyofsetup.com/
ok. RepairCommand was ommitted. Got it down to a very basic config:
?xml version=1.0 encoding=UTF-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
xmlns:util=http://schemas.microsoft.com/wix/UtilExtension;
Bundle Name=MyBootstrapper Version=1.0.0.0
Manufacturer=MyManufacturer
Hi,
Assume I have a bundle consisting of 1 MSI + 1 EXE and Exe doesn't support
repair. Is there a way to configure the exe that burn does no repair action
for the exe but for the MSI? like e.g.
ExePackage SourceFile=myExe.exe Permanent=yes AllowRepair=no /
MsiPackage SourceFile=myMsi.msi /
Best
Just don't set the ExePackage/@RepairCommand attribute. That should disable
repair for the exe.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bundle-Way-to-do-no-action-in-case-of-Repair-for-an-ExePackage-tp7584034p7584035.html
Sent from the
On 28-Feb-13 09:08, Tobias S wrote:
Assume I have a bundle consisting of 1 MSI + 1 EXE and Exe doesn't support
repair. Is there a way to configure the exe that burn does no repair action
for the exe but for the MSI? like e.g.
Just omit @RepairCommand -- if you don't tell it how to repair a
5 matches
Mail list logo