date:20120710

Re: [WiX-users] Issues when writing an installer using burn

2012-07-10 Thread Rob Mensching

Same error. Search for "error" in the Burn log and you're pretty certain to
find the error. In this case the MSI log file generated may provide more
details.

On Tue, Jul 10, 2012 at 8:41 PM, Sean Farrow
wrote:

> Hi Rob:
> That's strange, Having just checked programs/features, there doesn't
> appear to be any entries related to the product.
> Aditionally, another user has the following log:
> [02BC:0708][2012-07-09T13:32:24]: Burn v3.6.3102.0, Windows v6.1 (Build
> 7601: Service Pack 1), path: C:\work\eeb\srrt60\windows\surface reader
> installer\bin\Release\Surface Reader Installer.exe, cmdline:
> '-burn.unelevated BurnPipe.{EBB6F2F9-DEA4-472D-90D9-D6F5460F012B}
> {B3269642-50F1-4150-8BE3-04269A92CEC4} 3536'
> [02BC:0708][2012-07-09T13:32:24]: Initializing string variable
> 'InstallFolder' to value '[ProgramFiles6432Folder]Raised Bar\Surface Reader'
> [02BC:0708][2012-07-09T13:32:24]: Setting string variable 'WixBundleLog'
> to value 'C:\Users\tim\AppData\Local\Temp\Surface_Reader_20120709133224.log'
> [02BC:0708][2012-07-09T13:32:24]: Setting string variable
> 'WixBundleOriginalSource' to value 'C:\work\eeb\srrt60\windows\surface
> reader installer\bin\Release\Surface Reader Installer.exe'
> [02BC:0708][2012-07-09T13:32:25]: Setting string variable 'WixBundleName'
> to value 'Surface Reader'
> [02BC:0708][2012-07-09T13:32:25]: Detect 2 packages
> [02BC:0708][2012-07-09T13:32:25]: Detected package: SurfaceReader64.msi,
> state: Absent, cached: None
> [02BC:0708][2012-07-09T13:32:25]: Detected package: SurfaceReader32.msi,
> state: Absent, cached: None
> [02BC:0708][2012-07-09T13:32:25]: Detect complete, result: 0x0
> [02BC:0708][2012-07-09T13:32:39]: Plan 2 packages, action: Install
> [02BC:0708][2012-07-09T13:32:39]: Condition 'VersionNT64 >=v6.0' evaluates
> to true.
> [02BC:0708][2012-07-09T13:32:39]: Setting string variable
> 'WixBundleRollbackLog_SurfaceReader64.msi' to value
> 'C:\Users\tim\AppData\Local\Temp\Surface_Reader_20120709133224_0_SurfaceReader64.msi_rollback.log'
> [02BC:0708][2012-07-09T13:32:39]: Setting string variable
> 'WixBundleLog_SurfaceReader64.msi' to value
> 'C:\Users\tim\AppData\Local\Temp\Surface_Reader_20120709133224_0_SurfaceReader64.msi.log'
> [02BC:0708][2012-07-09T13:32:39]: Setting string variable
> 'WixBundleRollbackLog_SurfaceReader32.msi' to value
> 'C:\Users\tim\AppData\Local\Temp\Surface_Reader_20120709133224_1_SurfaceReader32.msi_rollback.log'
> [02BC:0708][2012-07-09T13:32:39]: Setting string variable
> 'WixBundleLog_SurfaceReader32.msi' to value
> 'C:\Users\tim\AppData\Local\Temp\Surface_Reader_20120709133224_1_SurfaceReader32.msi.log'
> [02BC:0708][2012-07-09T13:32:39]: Planned package: SurfaceReader64.msi,
> state: Absent, default requested: Present, ba requested: Present, execute:
> Install, rollback: Uninstall, cache: Yes, uncache: No, dependency: Register
> [02BC:0708][2012-07-09T13:32:39]: Planned package: SurfaceReader32.msi,
> state: Absent, default requested: Present, ba requested: Present, execute:
> Install, rollback: Uninstall, cache: Yes, uncache: No, dependency: Register
> [02BC:0708][2012-07-09T13:32:39]: Plan complete, result: 0x0
> [02BC:0708][2012-07-09T13:32:40]: Apply begin
> [0DD0:0BD8][2012-07-09T13:32:40]: Creating a system restore point.
> [0DD0:0BD8][2012-07-09T13:32:45]: Created a system restore point.
> [0DD0:0BD8][2012-07-09T13:32:45]: Caching bundle from:
> 'C:\Users\tim\AppData\Local\Temp\{a0b06f74-2bbf-4b09-9965-95b28122b818}\.be\Surface
> Reader Installer.exe' to: 'C:\ProgramData\Package
> Cache\{a0b06f74-2bbf-4b09-9965-95b28122b818}\Surface Reader Installer.exe'
> [0DD0:0BD8][2012-07-09T13:32:45]: Registering bundle dependency provider:
> {a0b06f74-2bbf-4b09-9965-95b28122b818}, version: 1.0.0.0
> [0DD0:08A4][2012-07-09T13:32:45]: Verified acquired payload:
> SurfaceReader64.msi at path: C:\ProgramData\Package
> Cache\.unverified\SurfaceReader64.msi, moving to: C:\ProgramData\Package
> Cache\{096AD882-6A32-442F-BDCF-12F7948DE5D4}v1.0.0.0\SurfaceReader64.msi.
> [0DD0:08A4][2012-07-09T13:32:45]: Verified acquired payload:
> SurfaceReader32.msi at path: C:\ProgramData\Package
> Cache\.unverified\SurfaceReader32.msi, moving to: C:\ProgramData\Package
> Cache\{096AD882-6A32-442F-BDCF-12F7948DE5D4}v1.0.0.0\SurfaceReader32.msi.
> [0DD0:0BD8][2012-07-09T13:32:45]: Applying execute package:
> SurfaceReader64.msi, action: Install, path: C:\ProgramData\Package
> Cache\{096AD882-6A32-442F-BDCF-12F7948DE5D4}v1.0.0.0\SurfaceReader64.msi,
> arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7"'
> [0DD0:0BD8][2012-07-09T13:33:26]: Registering package dependency provider:
> {096AD882-6A32-442F-BDCF-12F7948DE5D4}, version: 1.0.0.0, package:
> SurfaceReader64.msi
> [02BC:0708][2012-07-09T13:33:26]: Applied execute package:
> SurfaceReader64.msi, result: 0x0, restart: None
> [0DD0:0BD8][2012-07-09T13:33:26]: Registering dependency:
> {a0b06f74-2bbf-4b09-9965-95b28122b818} on package provider:
> {096AD882-6A32-442F-BDCF-12F7948DE5D4}, package: Surfa

Re: [WiX-users] Issues when writing an installer using burn

2012-07-10 Thread Sean Farrow

Hi Rob:
That's strange, Having just checked programs/features, there doesn't appear to 
be any entries related to the product.
Aditionally, another user has the following log:
[02BC:0708][2012-07-09T13:32:24]: Burn v3.6.3102.0, Windows v6.1 (Build 7601: 
Service Pack 1), path: C:\work\eeb\srrt60\windows\surface reader 
installer\bin\Release\Surface Reader Installer.exe, cmdline: '-burn.unelevated 
BurnPipe.{EBB6F2F9-DEA4-472D-90D9-D6F5460F012B} 
{B3269642-50F1-4150-8BE3-04269A92CEC4} 3536'
[02BC:0708][2012-07-09T13:32:24]: Initializing string variable 'InstallFolder' 
to value '[ProgramFiles6432Folder]Raised Bar\Surface Reader'
[02BC:0708][2012-07-09T13:32:24]: Setting string variable 'WixBundleLog' to 
value 'C:\Users\tim\AppData\Local\Temp\Surface_Reader_20120709133224.log'
[02BC:0708][2012-07-09T13:32:24]: Setting string variable 
'WixBundleOriginalSource' to value 'C:\work\eeb\srrt60\windows\surface reader 
installer\bin\Release\Surface Reader Installer.exe'
[02BC:0708][2012-07-09T13:32:25]: Setting string variable 'WixBundleName' to 
value 'Surface Reader'
[02BC:0708][2012-07-09T13:32:25]: Detect 2 packages
[02BC:0708][2012-07-09T13:32:25]: Detected package: SurfaceReader64.msi, state: 
Absent, cached: None
[02BC:0708][2012-07-09T13:32:25]: Detected package: SurfaceReader32.msi, state: 
Absent, cached: None
[02BC:0708][2012-07-09T13:32:25]: Detect complete, result: 0x0
[02BC:0708][2012-07-09T13:32:39]: Plan 2 packages, action: Install
[02BC:0708][2012-07-09T13:32:39]: Condition 'VersionNT64 >=v6.0' evaluates to 
true.
[02BC:0708][2012-07-09T13:32:39]: Setting string variable 
'WixBundleRollbackLog_SurfaceReader64.msi' to value 
'C:\Users\tim\AppData\Local\Temp\Surface_Reader_20120709133224_0_SurfaceReader64.msi_rollback.log'
[02BC:0708][2012-07-09T13:32:39]: Setting string variable 
'WixBundleLog_SurfaceReader64.msi' to value 
'C:\Users\tim\AppData\Local\Temp\Surface_Reader_20120709133224_0_SurfaceReader64.msi.log'
[02BC:0708][2012-07-09T13:32:39]: Setting string variable 
'WixBundleRollbackLog_SurfaceReader32.msi' to value 
'C:\Users\tim\AppData\Local\Temp\Surface_Reader_20120709133224_1_SurfaceReader32.msi_rollback.log'
[02BC:0708][2012-07-09T13:32:39]: Setting string variable 
'WixBundleLog_SurfaceReader32.msi' to value 
'C:\Users\tim\AppData\Local\Temp\Surface_Reader_20120709133224_1_SurfaceReader32.msi.log'
[02BC:0708][2012-07-09T13:32:39]: Planned package: SurfaceReader64.msi, state: 
Absent, default requested: Present, ba requested: Present, execute: Install, 
rollback: Uninstall, cache: Yes, uncache: No, dependency: Register
[02BC:0708][2012-07-09T13:32:39]: Planned package: SurfaceReader32.msi, state: 
Absent, default requested: Present, ba requested: Present, execute: Install, 
rollback: Uninstall, cache: Yes, uncache: No, dependency: Register
[02BC:0708][2012-07-09T13:32:39]: Plan complete, result: 0x0
[02BC:0708][2012-07-09T13:32:40]: Apply begin
[0DD0:0BD8][2012-07-09T13:32:40]: Creating a system restore point.
[0DD0:0BD8][2012-07-09T13:32:45]: Created a system restore point.
[0DD0:0BD8][2012-07-09T13:32:45]: Caching bundle from: 
'C:\Users\tim\AppData\Local\Temp\{a0b06f74-2bbf-4b09-9965-95b28122b818}\.be\Surface
 Reader Installer.exe' to: 'C:\ProgramData\Package 
Cache\{a0b06f74-2bbf-4b09-9965-95b28122b818}\Surface Reader Installer.exe'
[0DD0:0BD8][2012-07-09T13:32:45]: Registering bundle dependency provider: 
{a0b06f74-2bbf-4b09-9965-95b28122b818}, version: 1.0.0.0
[0DD0:08A4][2012-07-09T13:32:45]: Verified acquired payload: 
SurfaceReader64.msi at path: C:\ProgramData\Package 
Cache\.unverified\SurfaceReader64.msi, moving to: C:\ProgramData\Package 
Cache\{096AD882-6A32-442F-BDCF-12F7948DE5D4}v1.0.0.0\SurfaceReader64.msi.
[0DD0:08A4][2012-07-09T13:32:45]: Verified acquired payload: 
SurfaceReader32.msi at path: C:\ProgramData\Package 
Cache\.unverified\SurfaceReader32.msi, moving to: C:\ProgramData\Package 
Cache\{096AD882-6A32-442F-BDCF-12F7948DE5D4}v1.0.0.0\SurfaceReader32.msi.
[0DD0:0BD8][2012-07-09T13:32:45]: Applying execute package: 
SurfaceReader64.msi, action: Install, path: C:\ProgramData\Package 
Cache\{096AD882-6A32-442F-BDCF-12F7948DE5D4}v1.0.0.0\SurfaceReader64.msi, 
arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7"'
[0DD0:0BD8][2012-07-09T13:33:26]: Registering package dependency provider: 
{096AD882-6A32-442F-BDCF-12F7948DE5D4}, version: 1.0.0.0, package: 
SurfaceReader64.msi
[02BC:0708][2012-07-09T13:33:26]: Applied execute package: SurfaceReader64.msi, 
result: 0x0, restart: None
[0DD0:0BD8][2012-07-09T13:33:26]: Registering dependency: 
{a0b06f74-2bbf-4b09-9965-95b28122b818} on package provider: 
{096AD882-6A32-442F-BDCF-12F7948DE5D4}, package: SurfaceReader64.msi
[0DD0:0BD8][2012-07-09T13:33:26]: Applying execute package: 
SurfaceReader32.msi, action: Install, path: C:\ProgramData\Package 
Cache\{096AD882-6A32-442F-BDCF-12F7948DE5D4}v1.0.0.0\SurfaceReader32.msi, 
arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7"'
[0DD0:0BD8][2012-07-09T13:33:26]: Error 0x80

Re: [WiX-users] Issues when writing an installer using burn

2012-07-10 Thread Rob Mensching

Your MSI is failing to install:

 0x80070666Another version of this product is already installed.
Installation of this version cannot continue. To configure or remove the
existing version of this product, use Add/Remove Programs on the Control
Panel.

On Tue, Jul 10, 2012 at 8:01 PM, Sean Farrow
wrote:

> Hi Fokes:
> I'm just putting together an executable bootstrapper using burn.
> I have the following bundle:
> 
> http://schemas.microsoft.com/wix/2006/wi";>
>   
>   
>  Id="WixStandardBootstrapperApplication.RtfLicense" />
>  Value="[ProgramFiles6432Folder]Raised Bar\Surface Reader" />
> 
>DisplayInternalUI="yes" InstallCondition="VersionNT64 >=v6.0"/>
>   
> 
> 
> 
> When compiled and run, the install fails and I get the following log
> output:
> [080C:0560][2012-07-11T03:53:26]: Burn v3.6.3102.0, Windows v6.1 (Build
> 7601: Service Pack 1), path: C:\Work\srrt60\Surface Reader
> Installer\bin\Release\Surface Reader Installer.exe, cmdline:
> '-burn.unelevated BurnPipe.{64775B4A-E70F-4E33-BF63-AC37949186B0}
> {5317C24E-1339-459C-AB8C-B843A0896304} 3580'
> [080C:0560][2012-07-11T03:53:26]: Initializing string variable
> 'InstallFolder' to value '[ProgramFiles6432Folder]Raised Bar\Surface Reader'
> [080C:0560][2012-07-11T03:53:27]: Setting string variable 'WixBundleLog'
> to value
> 'C:\Users\Sean\AppData\Local\Temp\Surface_Reader_20120711035327.log'
> [080C:0560][2012-07-11T03:53:27]: Setting string variable
> 'WixBundleOriginalSource' to value 'C:\Work\srrt60\Surface Reader
> Installer\bin\Release\Surface Reader Installer.exe'
> [080C:0560][2012-07-11T03:53:27]: Setting string variable 'WixBundleName'
> to value 'Surface Reader'
> [080C:0560][2012-07-11T03:53:30]: Detect 2 packages
> [080C:0560][2012-07-11T03:53:30]: Detected package: SurfaceReader64.msi,
> state: Absent, cached: None
> [080C:0560][2012-07-11T03:53:30]: Detected package: SurfaceReader32.msi,
> state: Absent, cached: None
> [080C:0560][2012-07-11T03:53:30]: Detect complete, result: 0x0
> [080C:0C28][2012-07-11T03:53:40]: Setting string variable 'InstallFolder'
> to value 'C:\Program Files\Raised Bar\Surface Reader'
> [080C:0560][2012-07-11T03:53:43]: Plan 2 packages, action: Install
> [080C:0560][2012-07-11T03:53:43]: Condition 'VersionNT64 >=v6.0' evaluates
> to true.
> [080C:0560][2012-07-11T03:53:43]: Setting string variable
> 'WixBundleRollbackLog_SurfaceReader64.msi' to value
> 'C:\Users\Sean\AppData\Local\Temp\Surface_Reader_20120711035327_0_SurfaceReader64.msi_rollback.log'
> [080C:0560][2012-07-11T03:53:43]: Setting string variable
> 'WixBundleLog_SurfaceReader64.msi' to value
> 'C:\Users\Sean\AppData\Local\Temp\Surface_Reader_20120711035327_0_SurfaceReader64.msi.log'
> [080C:0560][2012-07-11T03:53:43]: Setting string variable
> 'WixBundleRollbackLog_SurfaceReader32.msi' to value
> 'C:\Users\Sean\AppData\Local\Temp\Surface_Reader_20120711035327_1_SurfaceReader32.msi_rollback.log'
> [080C:0560][2012-07-11T03:53:43]: Setting string variable
> 'WixBundleLog_SurfaceReader32.msi' to value
> 'C:\Users\Sean\AppData\Local\Temp\Surface_Reader_20120711035327_1_SurfaceReader32.msi.log'
> [080C:0560][2012-07-11T03:53:43]: Planned package: SurfaceReader64.msi,
> state: Absent, default requested: Present, ba requested: Present, execute:
> Install, rollback: Uninstall, cache: Yes, uncache: No, dependency: Register
> [080C:0560][2012-07-11T03:53:43]: Planned package: SurfaceReader32.msi,
> state: Absent, default requested: Present, ba requested: Present, execute:
> Install, rollback: Uninstall, cache: Yes, uncache: No, dependency: Register
> [080C:0560][2012-07-11T03:53:43]: Plan complete, result: 0x0
> [080C:0560][2012-07-11T03:53:43]: Apply begin
> [0DFC:1718][2012-07-11T03:53:43]: Creating a system restore point.
> [0DFC:1718][2012-07-11T03:54:51]: Created a system restore point.
> [0DFC:1718][2012-07-11T03:54:54]: Caching bundle from:
> 'C:\Users\Sean\AppData\Local\Temp\{a0b06f74-2bbf-4b09-9965-95b28122b818}\.be\Surface
> Reader Installer.exe' to: 'C:\ProgramData\Package
> Cache\{a0b06f74-2bbf-4b09-9965-95b28122b818}\Surface Reader Installer.exe'
> [0DFC:1718][2012-07-11T03:54:54]: Registering bundle dependency provider:
> {a0b06f74-2bbf-4b09-9965-95b28122b818}, version: 1.0.0.0
> [0DFC:139C][2012-07-11T03:54:55]: Verified acquired payload:
> SurfaceReader64.msi at path: C:\ProgramData\Package
> Cache\.unverified\SurfaceReader64.msi, moving to: C:\ProgramData\Package
> Cache\{096AD882-6A32-442F-BDCF-12F7948DE5D4}v1.0.0.0\SurfaceReader64.msi.
> [0DFC:139C][2012-07-11T03:54:55]: Verified acquired payload:
> SurfaceReader32.msi at path: C:\ProgramData\Package
> Cache\.unverified\SurfaceReader32.msi, moving to: C:\ProgramData\Package
> Cache\{096AD882-6A32-442F-BDCF-12F7948DE5D4}v1.0.0.0\SurfaceReader32.msi.
> [0DFC:1718][2012-07-11T03:54:55]: Applying execute package:
> SurfaceReader64.msi, action: Install, path: C:\ProgramData\Package
> Cache\{096

[WiX-users] Issues when writing an installer using burn

2012-07-10 Thread Sean Farrow

Hi Fokes:
I'm just putting together an executable bootstrapper using burn.
I have the following bundle:

http://schemas.microsoft.com/wix/2006/wi";>
  
  



  
  



When compiled and run, the install fails and I get the following log output:
[080C:0560][2012-07-11T03:53:26]: Burn v3.6.3102.0, Windows v6.1 (Build 7601: 
Service Pack 1), path: C:\Work\srrt60\Surface Reader 
Installer\bin\Release\Surface Reader Installer.exe, cmdline: '-burn.unelevated 
BurnPipe.{64775B4A-E70F-4E33-BF63-AC37949186B0} 
{5317C24E-1339-459C-AB8C-B843A0896304} 3580'
[080C:0560][2012-07-11T03:53:26]: Initializing string variable 'InstallFolder' 
to value '[ProgramFiles6432Folder]Raised Bar\Surface Reader'
[080C:0560][2012-07-11T03:53:27]: Setting string variable 'WixBundleLog' to 
value 'C:\Users\Sean\AppData\Local\Temp\Surface_Reader_20120711035327.log'
[080C:0560][2012-07-11T03:53:27]: Setting string variable 
'WixBundleOriginalSource' to value 'C:\Work\srrt60\Surface Reader 
Installer\bin\Release\Surface Reader Installer.exe'
[080C:0560][2012-07-11T03:53:27]: Setting string variable 'WixBundleName' to 
value 'Surface Reader'
[080C:0560][2012-07-11T03:53:30]: Detect 2 packages
[080C:0560][2012-07-11T03:53:30]: Detected package: SurfaceReader64.msi, state: 
Absent, cached: None
[080C:0560][2012-07-11T03:53:30]: Detected package: SurfaceReader32.msi, state: 
Absent, cached: None
[080C:0560][2012-07-11T03:53:30]: Detect complete, result: 0x0
[080C:0C28][2012-07-11T03:53:40]: Setting string variable 'InstallFolder' to 
value 'C:\Program Files\Raised Bar\Surface Reader'
[080C:0560][2012-07-11T03:53:43]: Plan 2 packages, action: Install
[080C:0560][2012-07-11T03:53:43]: Condition 'VersionNT64 >=v6.0' evaluates to 
true.
[080C:0560][2012-07-11T03:53:43]: Setting string variable 
'WixBundleRollbackLog_SurfaceReader64.msi' to value 
'C:\Users\Sean\AppData\Local\Temp\Surface_Reader_20120711035327_0_SurfaceReader64.msi_rollback.log'
[080C:0560][2012-07-11T03:53:43]: Setting string variable 
'WixBundleLog_SurfaceReader64.msi' to value 
'C:\Users\Sean\AppData\Local\Temp\Surface_Reader_20120711035327_0_SurfaceReader64.msi.log'
[080C:0560][2012-07-11T03:53:43]: Setting string variable 
'WixBundleRollbackLog_SurfaceReader32.msi' to value 
'C:\Users\Sean\AppData\Local\Temp\Surface_Reader_20120711035327_1_SurfaceReader32.msi_rollback.log'
[080C:0560][2012-07-11T03:53:43]: Setting string variable 
'WixBundleLog_SurfaceReader32.msi' to value 
'C:\Users\Sean\AppData\Local\Temp\Surface_Reader_20120711035327_1_SurfaceReader32.msi.log'
[080C:0560][2012-07-11T03:53:43]: Planned package: SurfaceReader64.msi, state: 
Absent, default requested: Present, ba requested: Present, execute: Install, 
rollback: Uninstall, cache: Yes, uncache: No, dependency: Register
[080C:0560][2012-07-11T03:53:43]: Planned package: SurfaceReader32.msi, state: 
Absent, default requested: Present, ba requested: Present, execute: Install, 
rollback: Uninstall, cache: Yes, uncache: No, dependency: Register
[080C:0560][2012-07-11T03:53:43]: Plan complete, result: 0x0
[080C:0560][2012-07-11T03:53:43]: Apply begin
[0DFC:1718][2012-07-11T03:53:43]: Creating a system restore point.
[0DFC:1718][2012-07-11T03:54:51]: Created a system restore point.
[0DFC:1718][2012-07-11T03:54:54]: Caching bundle from: 
'C:\Users\Sean\AppData\Local\Temp\{a0b06f74-2bbf-4b09-9965-95b28122b818}\.be\Surface
 Reader Installer.exe' to: 'C:\ProgramData\Package 
Cache\{a0b06f74-2bbf-4b09-9965-95b28122b818}\Surface Reader Installer.exe'
[0DFC:1718][2012-07-11T03:54:54]: Registering bundle dependency provider: 
{a0b06f74-2bbf-4b09-9965-95b28122b818}, version: 1.0.0.0
[0DFC:139C][2012-07-11T03:54:55]: Verified acquired payload: 
SurfaceReader64.msi at path: C:\ProgramData\Package 
Cache\.unverified\SurfaceReader64.msi, moving to: C:\ProgramData\Package 
Cache\{096AD882-6A32-442F-BDCF-12F7948DE5D4}v1.0.0.0\SurfaceReader64.msi.
[0DFC:139C][2012-07-11T03:54:55]: Verified acquired payload: 
SurfaceReader32.msi at path: C:\ProgramData\Package 
Cache\.unverified\SurfaceReader32.msi, moving to: C:\ProgramData\Package 
Cache\{096AD882-6A32-442F-BDCF-12F7948DE5D4}v1.0.0.0\SurfaceReader32.msi.
[0DFC:1718][2012-07-11T03:54:55]: Applying execute package: 
SurfaceReader64.msi, action: Install, path: C:\ProgramData\Package 
Cache\{096AD882-6A32-442F-BDCF-12F7948DE5D4}v1.0.0.0\SurfaceReader64.msi, 
arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7"'
[0DFC:1718][2012-07-11T03:55:37]: Registering package dependency provider: 
{096AD882-6A32-442F-BDCF-12F7948DE5D4}, version: 1.0.0.0, package: 
SurfaceReader64.msi
[080C:0560][2012-07-11T03:55:37]: Applied execute package: SurfaceReader64.msi, 
result: 0x0, restart: None
[0DFC:1718][2012-07-11T03:55:37]: Registering dependency: 
{a0b06f74-2bbf-4b09-9965-95b28122b818} on package provider: 
{096AD882-6A32-442F-BDCF-12F7948DE5D4}, package: SurfaceReader64.msi
[0DFC:1718][2012-07-11T03:55:

Re: [WiX-users] vs 2010 integration

2012-07-10 Thread Castro, Edwin G. (Hillsboro)

The Product.wxs is not modified by the automatic harvest functionality. A new 
temporary file in the intermediate directory (obj) is generated and included in 
the list of files to compile. This is why the harvested files show up in the 
MSI package as expected. Look in the obj directory for generated files and 
you'll find one with the harvested files.

Edwin G. Castro
Software Developer - Staff
Digital Channels
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
Please consider the environment before printing this e-mail


> -Original Message-
> From: Garry, Joseph [mailto:jga...@enghouse.com]
> Sent: Tuesday, July 10, 2012 1:00 PM
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] vs 2010 integration
> 
> I'm new to WiX and trying to determine if this tool will work for our 
> purposes.
> We're using VS 2010.
> In working through the instructions for Creating a Simple Setup under
> Working in Visual Studio, it appears that when I build the setup after adding
> the reference nothing is added to the Product.wxs file(Harvest is set to
> True). If I manually edit the file, the intellisense doesn't seem to be 
> working.
> However when I build the generated setup does seem to work correctly.
> Just wondering what I'm doing wrong, if anything, that the integration
> doesn't seem to be working quite right?
> --
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and threat
> landscape has changed and how IT managers can respond. Discussions will
> include endpoint security, mobile security and the latest in malware threats.
> http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] vs 2010 integration

2012-07-10 Thread Garry, Joseph

I'm new to WiX and trying to determine if this tool will work for our purposes.
We're using VS 2010.
In working through the instructions for Creating a Simple Setup under Working 
in Visual Studio, it appears that when I build the setup after adding the 
reference nothing is added to the Product.wxs file(Harvest is set to True). If 
I manually edit the file, the intellisense doesn't seem to be working. However 
when I build the generated setup does seem to work correctly.
Just wondering what I'm doing wrong, if anything, that the integration doesn't 
seem to be working quite right?
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] GACing .NET binaries to a specific GAC (.net 2.0 vs .net 4.0)

2012-07-10 Thread Garrett Serack

Hmm.

I've discovered the actual problem--which is actually quite a bit more 
troublesome.

Indeed, if I don't have a version of that assembly installed, the binary will 
get registered in the correct GAC. Unfortunately, if I have a version  of the 
assembly in the .NET 4.0 GAC, the 2.0 version just gets skipped altogether. 
That's uncool. (Clearly an MSI bug)

Beyond that, my binding policy assemblies are *always* getting installed into 
the .NET 4.0 GAC, not into the 2.0 GAC (regardless of the above 
condition)--oh--hmmm, that may be because of the version of the assembly linker 
(AL.EXE) I'm using. Yeah, that looks like it. 

So really, my problem is when I have two assemblies of the same name (with the 
same version), intended for different GACs. 

Nasty stuff. 

G

From: Dirk Räder [d...@raeder.cc]
Sent: Tuesday, July 10, 2012 6:18 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] GACing .NET binaries to a specific GAC (.net 2.0 vs 
.net 4.0)

Hi Garrett,

with our product we have some libraries that get installed into .NET
GAC. The GAC they are installed into is defined by the target
framework these assemblies are built for.
So, if you build them for .NET 3.5 or earlier, they are installed into
the .NET 2.0 GAC.
If they are build for .NET 4.0, they are installed into the .NET 4.0 GAC.

Regards, Dirk


2012/7/9 Garrett Serack :
> Hey, I was wondering if it's possible when creating an installer to install a 
> .NET assembly that installs a given assembly to a particular GAC.
>
> I've got an assembly that I'd like installed to the .NET 2.0 GAC, but 
> apparently it just wants to install it to the 4.0 GAC.
>
> Any ideas?
>
> --
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users






--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Trying to create patch, getting PYRO0227 error.

2012-07-10 Thread Pavol Kovalik

Thanks. I've eventually figured out what was the problem: not the patching
process, but the way I was trying to generate the transform file. Obviously
the metadata in .wixmst file are not as important as contents of the files.
I could not create patch using only single working copy of project and just
keeping .wixpdb files.

So, I've solved this by using administrative installs of .msi istead of
.wixpdb files.

--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Trying-to-create-patch-getting-PYRO0227-error-tp7579233p7579375.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] .NET 4 pre-req in WixNetFxExtension

2012-07-10 Thread Nick Ramirez

I see. What would Result.Ok do then in this situation? Is there a place that
lists what the different result codes do, out of curiosity?

--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/NET-4-pre-req-in-WixNetFxExtension-tp7579058p7579374.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Should balinfo.h be included in sdk/inc?

2012-07-10 Thread Darwin Baines

https://sourceforge.net/tracker/?func=detail&aid=3542020&group_id=105970&atid=642714


Date: Tue, 10 Jul 2012 00:28:17 -0400

From: Bob Arnson

Subject: Re: [WiX-users] Should balinfo.h be included in sdk/inc?



On 09-Jul-12 17:26, Darwin Baines wrote:

> You can't build WixStdBA without balinfo.h.

>

> Should it be included in the binary distribution under sdk/inc?

Yes. Please file a bug so it doesn't get lost in e-mail.



--

sig://boB

http://joyofsetup.com/





--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] GACing .NET binaries to a specific GAC (.net 2.0 vs .net 4.0)

2012-07-10 Thread Dirk Räder

Hi Garrett,

with our product we have some libraries that get installed into .NET
GAC. The GAC they are installed into is defined by the target
framework these assemblies are built for.
So, if you build them for .NET 3.5 or earlier, they are installed into
the .NET 2.0 GAC.
If they are build for .NET 4.0, they are installed into the .NET 4.0 GAC.

Regards, Dirk


2012/7/9 Garrett Serack :
> Hey, I was wondering if it's possible when creating an installer to install a 
> .NET assembly that installs a given assembly to a particular GAC.
>
> I've got an assembly that I'd like installed to the .NET 2.0 GAC, but 
> apparently it just wants to install it to the 4.0 GAC.
>
> Any ideas?
>
> --
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Burn: Planning: package customization

2012-07-10 Thread Kannan24

Hi,

Please find the log file details, while uninstalling the setup.

___

[0F50:177C][2012-07-10T07:05:40]: Burn v3.6.2928.0, Windows v6.1 (Build
7600: Service Pack 0), path: C:\ProgramData\Package
Cache\{7215c318-042d-488a-9b21-0cbe9727ac6b}\essentialstudio.exe, cmdline:
'/uninstall'
[0F50:177C][2012-07-10T07:05:41]: Setting string variable 'WixBundleLog' to
value
'C:\Users\kannanns\AppData\Local\Temp\essentialstudio_20120710070541.log'
[0F50:177C][2012-07-10T07:05:41]: Loading managed bootstrapper application.
[0F50:177C][2012-07-10T07:05:42]: Creating BA thread to run asynchronously.
[0F50:13C0][2012-07-10T07:05:56]: Setting string variable 'AppPath' to value
''
[0F50:13C0][2012-07-10T07:05:56]: Setting string variable 'SAMPLESPATH' to
value ''
[0F50:13C0][2012-07-10T07:05:58]: Setting string variable
'UNISTALLEXITSASSEMBLIES' to value 'TRUE'
[0F50:177C][2012-07-10T07:05:58]: Detect 1 packages
[0F50:177C][2012-07-10T07:05:58]: Detected related bundle:
{0b9b78b4-c30d-4cda-a592-182e2f68796b}, type: Upgrade, scope: PerMachine,
version: 10.2.0.80, operation: None
[0F50:177C][2012-07-10T07:05:58]: Detected related bundle:
{ba8dad1c-886a-4926-9d66-c486b7129cec}, type: Upgrade, scope: PerMachine,
version: 10.2.0.80, operation: None
[0F50:177C][2012-07-10T07:05:58]: Detected related bundle:
{bee6bd80-095f-4788-adc7-f6503cbb9a90}, type: Upgrade, scope: PerMachine,
version: 10.2.0.80, operation: None
[0F50:177C][2012-07-10T07:05:58]: Detected package: testsetup, state:
Present, cached: Complete
[0F50:177C][2012-07-10T07:05:58]: Detected package: testsetup, feature:
ProductFeature2, state: Local
[0F50:177C][2012-07-10T07:05:58]: Detected package: testsetup, feature:
imageFeature22, state: Local
[0F50:177C][2012-07-10T07:05:58]: Detected package: testsetup, feature:
imageFeature4, state: Local
[0F50:177C][2012-07-10T07:05:58]: Detected package: testsetup, feature:
imageFeature6, state: Local
[0F50:177C][2012-07-10T07:06:00]: Detect complete, result: 0x0
[0F50:177C][2012-07-10T07:06:00]: Plan 1 packages, action: Uninstall
[0F50:177C][2012-07-10T07:06:00]: Planned related bundle:
{bee6bd80-095f-4788-adc7-f6503cbb9a90}, type: Upgrade, default requested:
None, ba requested: None, execute: None, rollback: None, dependency: None
[0F50:177C][2012-07-10T07:06:00]: Planned related bundle:
{ba8dad1c-886a-4926-9d66-c486b7129cec}, type: Upgrade, default requested:
None, ba requested: None, execute: None, rollback: None, dependency: None
[0F50:177C][2012-07-10T07:06:00]: Planned related bundle:
{0b9b78b4-c30d-4cda-a592-182e2f68796b}, type: Upgrade, default requested:
None, ba requested: None, execute: None, rollback: None, dependency: None
[0F50:177C][2012-07-10T07:06:00]: Planned package: testsetup, state:
Present, default requested: None, ba requested: None, execute: None,
rollback: None, cache: No, uncache: No, dependency: Unregister
[0F50:177C][2012-07-10T07:06:00]: Plan complete, result: 0x0
[0F50:177C][2012-07-10T07:06:00]: Apply begin
[179C:15E8][2012-07-10T07:06:02]: Creating a system restore point.
[179C:15E8][2012-07-10T07:06:02]: Could not create system restore point,
error: 0x80070422. Continuing...
[179C:15E8][2012-07-10T07:06:02]: Removed dependency:
{7215c318-042d-488a-9b21-0cbe9727ac6b} on package provider:
{11A1799C-E013-463E-8693-BD10E6BDB5F2}, package testsetup
[179C:15E8][2012-07-10T07:06:02]: Removed bundle dependency provider:
{7215c318-042d-488a-9b21-0cbe9727ac6b}
[179C:15E8][2012-07-10T07:06:02]: Removing cached bundle:
{7215c318-042d-488a-9b21-0cbe9727ac6b}, from path: C:\ProgramData\Package
Cache\{7215c318-042d-488a-9b21-0cbe9727ac6b}\
[0F50:177C][2012-07-10T07:06:02]: Apply complete, result: 0x0, restart:
None, ba requested restart:  No
[0F50:177C][2012-07-10T07:06:02]: Apply begin
[179C:15E8][2012-07-10T07:06:02]: Creating a system restore point.
[179C:15E8][2012-07-10T07:06:02]: Could not create system restore point,
error: 0x80070422. Continuing...
[179C:15E8][2012-07-10T07:06:02]: Error 0x80070002: Failed to open
registration key.
[179C:15E8][2012-07-10T07:06:02]: Error 0x80070002: Failed to suspend
registration session.
[0F50:177C][2012-07-10T07:06:02]: Error 0x80070002: Failed to resume
registration session in per-machine process.
[0F50:177C][2012-07-10T07:06:02]: Error 0x80070002: Failed to register
bundle.
[0F50:177C][2012-07-10T07:06:02]: Apply complete, result: 0x80070002,
restart: None, ba requested restart:  No
__

Please help to fix the uninstall.

Thanks,
Kannan

--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Planning-package-customization-tp6040489p7579371.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Live Security Virtual Conference
Exclusive live event will cov

Re: [WiX-users] Bundle Variable Persisted attribute

2012-07-10 Thread Neil Sleightholm

I couldn't find a bug or feature request for this so I have added one - 3541950.

Neil

-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com] 
Sent: 10 July 2012 08:52
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Bundle Variable Persisted attribute

Variable/@Persisted makes the "Remember Property Pattern" (
http://robmensching.com/blog/posts/2010/5/2/The-WiX-toolsets-Remember-Property-pattern)
unnecessary for a single Bundle. What you want is the related Bundle solution 
that does not exist in Burn v3.6.

On Tue, Jul 10, 2012 at 12:30 AM, Neil Sleightholm wrote:

> So is that other executions of the same installation e.g. on repair or 
> uninstall?
>
> What I was after was a way of saving the install folder if someone 
> changes it so that when they upgrade it installs to the same folder - 
> will I have to do that in the MSI and read the value back in the bundle?
>
> Neil
>
> -Original Message-
> From: Rob Mensching [mailto:r...@robmensching.com]
> Sent: 10 July 2012 08:21
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Bundle Variable Persisted attribute
>
> It persists the Variable for future executions of the Bundle. It is 
> not currently possible to access persisted Variables for other Bundles 
> (although I believe there is a bug open to add the functionality for 
> related Bundles).
>
> On Mon, Jul 9, 2012 at 11:20 PM, Neil Sleightholm  >wrote:
>
> > What does the bundle Variable/@Persisted attribute do? I would have 
> > expected it to store the value somewhere so it can be re-read the 
> > next time the application is installed but there doesn't seem to be 
> > any documentation on how to do that.
> >
> > Neil
> >
> > Neil Sleightholm
> > X2 Systems Limited
> > n...@x2systems.com
> >
> >
> > 
> > --
> > 
> > Live Security Virtual Conference
> > Exclusive live event will cover all the ways today's security and 
> > threat landscape has changed and how IT managers can respond.
> > Discussions will include endpoint security, mobile security and the 
> > latest in malware threats.
> > http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> > ___
> > WiX-users mailing list
> > WiX-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wix-users
> >
>
>
>
> --
> virtually,
>
>Rob Mensching
>http://RobMensching.com LLC
>
> --
> 
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and 
> threat landscape has changed and how IT managers can respond. 
> Discussions will include endpoint security, mobile security and the 
> latest in malware threats. 
> http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
>
>
>
> --
> 
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and 
> threat landscape has changed and how IT managers can respond. 
> Discussions will include endpoint security, mobile security and the 
> latest in malware threats. 
> http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>



--
virtually,

   Rob Mensching
   http://RobMensching.com LLC
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and threat 
landscape has changed and how IT managers can respond. Discussions will include 
endpoint security, mobile security and the latest in malware threats. 
http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users




--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Bundle Variable Persisted attribute

2012-07-10 Thread Rob Mensching

Variable/@Persisted makes the "Remember Property Pattern" (
http://robmensching.com/blog/posts/2010/5/2/The-WiX-toolsets-Remember-Property-pattern)
unnecessary for a single Bundle. What you want is the related Bundle
solution that does not exist in Burn v3.6.

On Tue, Jul 10, 2012 at 12:30 AM, Neil Sleightholm wrote:

> So is that other executions of the same installation e.g. on repair or
> uninstall?
>
> What I was after was a way of saving the install folder if someone changes
> it so that when they upgrade it installs to the same folder - will I have
> to do that in the MSI and read the value back in the bundle?
>
> Neil
>
> -Original Message-
> From: Rob Mensching [mailto:r...@robmensching.com]
> Sent: 10 July 2012 08:21
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Bundle Variable Persisted attribute
>
> It persists the Variable for future executions of the Bundle. It is not
> currently possible to access persisted Variables for other Bundles
> (although I believe there is a bug open to add the functionality for
> related Bundles).
>
> On Mon, Jul 9, 2012 at 11:20 PM, Neil Sleightholm  >wrote:
>
> > What does the bundle Variable/@Persisted attribute do? I would have
> > expected it to store the value somewhere so it can be re-read the next
> > time the application is installed but there doesn't seem to be any
> > documentation on how to do that.
> >
> > Neil
> >
> > Neil Sleightholm
> > X2 Systems Limited
> > n...@x2systems.com
> >
> >
> > --
> > 
> > Live Security Virtual Conference
> > Exclusive live event will cover all the ways today's security and
> > threat landscape has changed and how IT managers can respond.
> > Discussions will include endpoint security, mobile security and the
> > latest in malware threats.
> > http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> > ___
> > WiX-users mailing list
> > WiX-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wix-users
> >
>
>
>
> --
> virtually,
>
>Rob Mensching
>http://RobMensching.com LLC
>
> --
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and threat
> landscape has changed and how IT managers can respond. Discussions will
> include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
>
>
>
> --
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>



-- 
virtually,

   Rob Mensching
   http://RobMensching.com LLC
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Bundle Variable Persisted attribute

2012-07-10 Thread Neil Sleightholm

So is that other executions of the same installation e.g. on repair or 
uninstall?

What I was after was a way of saving the install folder if someone changes it 
so that when they upgrade it installs to the same folder - will I have to do 
that in the MSI and read the value back in the bundle?

Neil

-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com] 
Sent: 10 July 2012 08:21
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Bundle Variable Persisted attribute

It persists the Variable for future executions of the Bundle. It is not 
currently possible to access persisted Variables for other Bundles (although I 
believe there is a bug open to add the functionality for related Bundles).

On Mon, Jul 9, 2012 at 11:20 PM, Neil Sleightholm wrote:

> What does the bundle Variable/@Persisted attribute do? I would have 
> expected it to store the value somewhere so it can be re-read the next 
> time the application is installed but there doesn't seem to be any 
> documentation on how to do that.
>
> Neil
>
> Neil Sleightholm
> X2 Systems Limited
> n...@x2systems.com
>
>
> --
> 
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and 
> threat landscape has changed and how IT managers can respond. 
> Discussions will include endpoint security, mobile security and the 
> latest in malware threats. 
> http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>



--
virtually,

   Rob Mensching
   http://RobMensching.com LLC
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and threat 
landscape has changed and how IT managers can respond. Discussions will include 
endpoint security, mobile security and the latest in malware threats. 
http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users




--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Bundle Variable Persisted attribute

2012-07-10 Thread Rob Mensching

It persists the Variable for future executions of the Bundle. It is not
currently possible to access persisted Variables for other Bundles
(although I believe there is a bug open to add the functionality for
related Bundles).

On Mon, Jul 9, 2012 at 11:20 PM, Neil Sleightholm wrote:

> What does the bundle Variable/@Persisted attribute do? I would have
> expected it to store the value somewhere so it can be re-read the next time
> the application is installed but there doesn't seem to be any documentation
> on how to do that.
>
> Neil
>
> Neil Sleightholm
> X2 Systems Limited
> n...@x2systems.com
>
>
> --
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>



-- 
virtually,

   Rob Mensching
   http://RobMensching.com LLC
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Issues when writing an installer using burn

Re: [WiX-users] Issues when writing an installer using burn

Re: [WiX-users] Issues when writing an installer using burn

[WiX-users] Issues when writing an installer using burn

Re: [WiX-users] vs 2010 integration

[WiX-users] vs 2010 integration

Re: [WiX-users] GACing .NET binaries to a specific GAC (.net 2.0 vs .net 4.0)

Re: [WiX-users] Trying to create patch, getting PYRO0227 error.

Re: [WiX-users] .NET 4 pre-req in WixNetFxExtension

Re: [WiX-users] Should balinfo.h be included in sdk/inc?

Re: [WiX-users] GACing .NET binaries to a specific GAC (.net 2.0 vs .net 4.0)

Re: [WiX-users] Burn: Planning: package customization

Re: [WiX-users] Bundle Variable Persisted attribute

Re: [WiX-users] Bundle Variable Persisted attribute

Re: [WiX-users] Bundle Variable Persisted attribute

Re: [WiX-users] Bundle Variable Persisted attribute

16 matches

Site Navigation

Mail list logo

Footer information