Re: [WiX-users] Bundle: Way to do no action in case of Repair for an ExePackage

2013-03-16 Thread Bob Arnson 
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/


--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Bundle: Way to do no action in case of Repair for an ExePackage

2013-03-01 Thread Tobias S 
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
UpgradeCode=0bbc7bb6-b024-405f-a6bb-1b6c9e3a11be
BootstrapperApplicationRef
Id=WixStandardBootstrapperApplication.RtfLicense /
Chain
  ExePackage SourceFile=c:\WinPcap_4_1_2.exe /
  MsiPackage SourceFile=c:\7z920-x64.msi /
/Chain
  /Bundle
/Wix


Despite ommitted burn tries to install the ExePackage WinPcap_4_1_2.exe in
case of repair if I read log file correct. (tested on w7 x64 based on wix
3.6 RTM + w8x64 based on wix 3.7 RTM). Following Log from wix 3.6 - 3.7 log
simmilar:

[0B80:0B6C][2013-03-01T01:12:27]: Applying execute package:
WinPcap_4_1_2.exe, action: Install, path: C:\ProgramData\Package
Cache\5BBDCE5C2AD5423BA023B1272301A7FB49279B16\WinPcap_4_1_2.exe,
arguments: 'C:\ProgramData\Package
Cache\5BBDCE5C2AD5423BA023B1272301A7FB49279B16\WinPcap_4_1_2.exe'

[09D4:09E8][2013-03-01T01:12:16]: Burn v3.6.3303.0, Windows v6.1 (Build
7600: Service Pack 0), path: C:\Users\admin\Desktop\Bootstrapper5.exe,
cmdline: ''
[09D4:09E8][2013-03-01T01:12:16]: Setting string variable 'WixBundleLog' to
value 'C:\Users\admin\AppData\Local\Temp\MyBootstrapper_20130301011216.log'
[09D4:09E8][2013-03-01T01:12:16]: Setting string variable
'WixBundleOriginalSource' to value
'C:\Users\admin\Desktop\Bootstrapper5.exe'
[09D4:09E8][2013-03-01T01:12:16]: Detect 2 packages
[09D4:09E8][2013-03-01T01:12:16]: Detected package: WinPcap_4_1_2.exe,
state: Absent, cached: Complete
[09D4:09E8][2013-03-01T01:12:16]: Detected package: _7z920_x64.msi, state:
Present, cached: Complete
[09D4:09E8][2013-03-01T01:12:16]: Detect complete, result: 0x0
[09D4:09E8][2013-03-01T01:12:18]: Plan 2 packages, action: Repair
[09D4:09E8][2013-03-01T01:12:18]: Skipping dependency registration on
package with no dependency providers: WinPcap_4_1_2.exe
[09D4:09E8][2013-03-01T01:12:18]: Setting string variable
'WixBundleLog_WinPcap_4_1_2.exe' to value
'C:\Users\admin\AppData\Local\Temp\MyBootstrapper_20130301011216_0_WinPcap_4_1_2.exe.log'
[09D4:09E8][2013-03-01T01:12:18]: Setting string variable
'WixBundleRollbackLog_WinPcap_4_1_2.exe' to value
'C:\Users\admin\AppData\Local\Temp\MyBootstrapper_20130301011216_0_WinPcap_4_1_2.exe_rollback.log'
[09D4:09E8][2013-03-01T01:12:18]: Setting string variable
'WixBundleLog__7z920_x64.msi' to value
'C:\Users\admin\AppData\Local\Temp\MyBootstrapper_20130301011216_1__7z920_x64.msi.log'
[09D4:09E8][2013-03-01T01:12:18]: Planned package: WinPcap_4_1_2.exe,
state: Absent, default requested: Repair, ba requested: Repair, execute:
Install, rollback: Uninstall, cache: No, uncache: No, dependency: None
[09D4:09E8][2013-03-01T01:12:18]: Planned package: _7z920_x64.msi, state:
Present, default requested: Repair, ba requested: Repair, execute: Repair,
rollback: None, cache: No, uncache: No, dependency: Register
[09D4:09E8][2013-03-01T01:12:18]: Plan complete, result: 0x0
[09D4:09E8][2013-03-01T01:12:18]: Apply begin
[0B80:0B6C][2013-03-01T01:12:20]: Creating a system restore point.
[0B80:0B6C][2013-03-01T01:12:27]: Created a system restore point.
[0B80:0A94][2013-03-01T01:12:27]: Verified existing payload:
WinPcap_4_1_2.exe at path: C:\ProgramData\Package
Cache\5BBDCE5C2AD5423BA023B1272301A7FB49279B16\WinPcap_4_1_2.exe.
[0B80:0A94][2013-03-01T01:12:27]: Verified existing payload: _7z920_x64.msi
at path: C:\ProgramData\Package
Cache\{23170F69-40C1-2702-0920-0100}v9.20.00.0\7z920-x64.msi.
[0B80:0B6C][2013-03-01T01:12:27]: Applying execute package:
WinPcap_4_1_2.exe, action: Install, path: C:\ProgramData\Package
Cache\5BBDCE5C2AD5423BA023B1272301A7FB49279B16\WinPcap_4_1_2.exe,
arguments: 'C:\ProgramData\Package
Cache\5BBDCE5C2AD5423BA023B1272301A7FB49279B16\WinPcap_4_1_2.exe'
[0B80:0B6C][2013-03-01T01:12:41]: Error 0x80070001: Process returned error:
0x1
[0B80:0B6C][2013-03-01T01:12:41]: Error 0x80070001: Failed to execute EXE
package.
[09D4:09E8][2013-03-01T01:12:41]: Error 0x80070001: Failed to configure
per-machine EXE package.
[09D4:09E8][2013-03-01T01:12:41]: Applied execute package:
WinPcap_4_1_2.exe, result: 0x80070001, restart: None
[09D4:09E8][2013-03-01T01:12:41]: Error 0x80070001: Failed to execute EXE
package.
[09D4:09E8][2013-03-01T01:12:41]: Apply complete, result: 0x80070001,
restart: None, ba requested restart:  No
[09D4:09E8][2013-03-01T01:12:43]: Shutting down, exit code: 0x80070001
[09D4:09E8][2013-03-01T01:12:43]: Variable: WixBundleAction = 6
[09D4:09E8][2013-03-01T01:12:43]: Variable: WixBundleElevated = 1
[09D4:09E8][2013-03-01T01:12:43]: Variable: WixBundleInstalled = 1
[09D4:09E8][2013-03-01T01:12:43]: Variable: WixBundleLog =
C:\Users\admin\AppData\Local\Temp\MyBootstrapper_20130301011216.log
[09D4:09E8][2013-03-01T01:12:43]: Variable: WixBundleLog__7z920_x64.msi =

[WiX-users] Bundle: Way to do no action in case of Repair for an ExePackage

2013-02-28 Thread Tobias S 
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 Regards,
Tobias
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Bundle: Way to do no action in case of Repair for an ExePackage

2013-02-28 Thread jhennessey 
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 wix-users mailing list archive at Nabble.com.

--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Bundle: Way to do no action in case of Repair for an ExePackage

2013-02-28 Thread Bob Arnson 
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 
package, Burn won't try.

-- 
sig://boB
http://joyofsetup.com/


--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users