[WiX-users] [nik] Issue with Burn installer
I have an installer that uses Burn. If I rebuild the installer without
changing any content and then run that installer it will install another
version alongside an existing one?
Using the individual MSI installers there is no issue with upgrades. This only
occurs when running the burn installer that has been rebuilt. Does anyone know
why this occurs and what can be done to fix it?
I have read that burn should first uninstall a current version then reinstall,
but I do not see this occurring. Log from the burn installer:
[2DF0:1360][2013-06-13T00:30:48]i001: Burn v3.7.1611.0, Windows v6.1 (Build
7601: Service Pack 1), path: elvsvc.exe, cmdline: '/log ib.log'
[2DF0:1360][2013-06-13T00:30:48]i000: Initializing string variable 'DISPLAYVER'
to value '1.0.1'
[2DF0:1360][2013-06-13T00:30:48]i000: Initializing string variable 'VERSION' to
value '1.0.1.1'
[2DF0:1360][2013-06-13T00:30:48]i000: Setting string variable 'WixBundleLog' to
value 'ib.log'
[2DF0:1360][2013-06-13T00:30:48]i000: Setting string variable
'WixBundleOriginalSource' to value 'elvsvc.exe'
[2DF0:1360][2013-06-13T00:30:48]i052: Condition 'VersionNT = v5.1' evaluates
to true.
[2DF0:1360][2013-06-13T00:30:48]i000: Setting string variable 'WixBundleName'
to value 'Test'
[2DF0:1360][2013-06-13T00:30:48]i100: Detect begin, 2 packages
[2DF0:1360][2013-06-13T00:30:48]i102: Detected related bundle:
{8eeeb531-9a26-48f5-a1f7-d6a59e05ef06}, type: Upgrade, scope: PerMachine,
version: 1.0.1.1, operation: None
[2DF0:1360][2013-06-13T00:30:48]i103: Detected related package:
{2F852825-CDDA-4FC4-B0D3-ABC4660BB139}, scope: PerMachine, version: 1.0.1.1,
language: 0 operation: MajorUpgrade
[2DF0:1360][2013-06-13T00:30:48]i101: Detected package: ElvSvc32, state:
Absent, cached: None
[2DF0:1360][2013-06-13T00:30:48]i101: Detected package: ElvSvc64, state:
Present, cached: Complete
[2DF0:1360][2013-06-13T00:30:48]i199: Detect complete, result: 0x0
[2DF0:1360][2013-06-13T00:30:55]i200: Plan begin, 2 packages, action: Install
[2DF0:1360][2013-06-13T00:30:55]i052: Condition '(NOT VersionNT64)' evaluates
to false.
[2DF0:1360][2013-06-13T00:30:55]i052: Condition 'VersionNT64' evaluates to true.
[2DF0:1360][2013-06-13T00:30:55]i201: Planned package: ElvSvc32, state: Absent,
default requested: Absent, ba requested: Absent, execute: None, rollback: None,
cache: No, uncache: No, dependency: None
[2DF0:1360][2013-06-13T00:30:55]i201: Planned package: ElvSvc64, state:
Present, default requested: Present, ba requested: Present, execute: None,
rollback: None, cache: No, uncache: No, dependency: Register
[2DF0:1360][2013-06-13T00:30:55]i207: Planned related bundle:
{8eeeb531-9a26-48f5-a1f7-d6a59e05ef06}, type: Upgrade, default requested: None,
ba requested: None, execute: None, rollback: None, dependency: None
[2DF0:1360][2013-06-13T00:30:55]i299: Plan complete, result: 0x0
[2DF0:1360][2013-06-13T00:30:55]i300: Apply begin
[2FA4:29FC][2013-06-13T00:30:58]i360: Creating a system restore point.
[2FA4:29FC][2013-06-13T00:31:03]i361: Created a system restore point.
[2FA4:29FC][2013-06-13T00:31:04]i000: Caching bundle from:
'C:\Users\NTWERD~1\AppData\Local\Temp\{f55ab761-afb5-4e7f-a790-0427ec346d25}\.be\bundle.exe'
to: 'C:\ProgramData\Package
Cache\{f55ab761-afb5-4e7f-a790-0427ec346d25}\bundle.exe'
[2FA4:29FC][2013-06-13T00:31:04]i320: Registering bundle dependency provider:
{f55ab761-afb5-4e7f-a790-0427ec346d25}, version: 1.0.1.1
[2FA4:29FC][2013-06-13T00:31:04]i323: Registering package dependency provider:
{2F852825-CDDA-4FC4-B0D3-ABC4660BB139}, version: 1.0.1.1, package: ElvSvc64
[2FA4:29FC][2013-06-13T00:31:04]i325: Registering dependency:
{f55ab761-afb5-4e7f-a790-0427ec346d25} on package provider:
{2F852825-CDDA-4FC4-B0D3-ABC4660BB139}, package: ElvSvc64
[2DF0:1360][2013-06-13T00:31:04]i399: Apply complete, result: 0x0, restart:
None, ba requested restart: No
[2DF0:1360][2013-06-13T00:31:07]i500: Shutting down, exit code: 0x0
[2DF0:1360][2013-06-13T00:31:07]i410: Variable: DISPLAYVER = 1.0.1
[2DF0:1360][2013-06-13T00:31:07]i410: Variable: VERSION = 1.0.1.1
[2DF0:1360][2013-06-13T00:31:07]i410: Variable: VersionNT = 6.1.0.0
[2DF0:1360][2013-06-13T00:31:07]i410: Variable: VersionNT64 = 6.1.0.0
[2DF0:1360][2013-06-13T00:31:07]i410: Variable: WixBundleAction = 4
[2DF0:1360][2013-06-13T00:31:07]i410: Variable: WixBundleElevated = 1
[2DF0:1360][2013-06-13T00:31:07]i410: Variable: WixBundleInstalled = 0
[2DF0:1360][2013-06-13T00:31:07]i410: Variable: WixBundleLog = ib.log
[2DF0:1360][2013-06-13T00:31:07]i410: Variable: WixBundleManufacturer = Me
[2DF0:1360][2013-06-13T00:31:07]i410: Variable: WixBundleName = Test
[2DF0:1360][2013-06-13T00:31:07]i410: Variable: WixBundleOriginalSource =
elvsvc.exe
[2DF0:1360][2013-06-13T00:31:07]i410: Variable: WixBundleProviderKey =
{f55ab761-afb5-4e7f-a790-0427ec346d25}
[2DF0:1360][2013-06-13T00:31:07]i410: Variable: WixBundleTag =
[2DF0:1360][2013-06-13T00:31:07]i410: Variable: WixBundleVersion = 1.0.1.1
[WiX-users] Can we package html files?
Hi Experts, My second day using WiX and I ran into this challenge. I have a bunch of html,css and js files (200+) organized in nested folder structure. Is it possible to use wix for packaging these files and then run this setup on another machine to install the same folder structure and files? Your expert guidance will be much appreciated. -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Using Default Ui merge with wixUi_Installdir
hi, I created a default ui for my changes,i need to merge the ui with wixui_installdir how is to possible, thanks regards, Chaitanya. -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] using a input property
Hi, I found some ways to use the value inserted in a input control: - I can set a property with the input value; - I can use the publish tag to perform actions such as a setproperty making use of the inserted value; I have a couple of questions: - Is the publish tag the only way to perform an action after a user input interface event takes place? - Is it possible to use a user inserted value to do actions such as a registry search? Are custom actions needed to do so or this can be done with plain wix? Thanks in advance :) -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/using-a-input-property-tp7586501.html Sent from the wix-users mailing list archive at Nabble.com. -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Read an Installed software Path from Registry update in Registry
hi, I need to read an Apache Software installed path from Registry.i need to update that path in my main registry Any suggestions Acceptable. Thanks Regrds, chaitanya. -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix help
http://wyrdfish.wordpress.com/2011/01/05/32-and-64-bit-msis-from-a-single-sou rce-file/ -Original Message- From: Subbiah Ganesan [mailto:subbiahtv...@gmail.com] Sent: 13 June 2013 06:47 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Wix help Use wix preprocessor directives to distinguish 32 bit and 64 bit requirements and build twice changing the preprocessor variable. On Thu, Jun 13, 2013 at 10:24 AM, Vik Jairath vikjair...@hotmail.comwrote: Hello, I'm new to wix and I would appreciate some help with an issue i'm encountering. I have a Product.wxs file that has 32 bit components. This is run on 64 bit and 32 bit platforms. I now need to use the same .wxs file but with some added dlls for the 64 bit platform(need to be installed to program files instead of program files (x86). I'd like to do this with the same .wxs file but generate two msi's. Is there an easy way to do this? I'm using Nant. Thanks in advance. -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - - This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Asia error
I usually received this message on windows server 2003 when the windows imaging component is missing... -Ursprüngliche Nachricht- Von: Rob Mensching [mailto:r...@robmensching.com] Gesendet: Mittwoch, 12. Juni 2013 16:19 An: General discussion for Windows Installer XML toolset. Betreff: Re: [WiX-users] Asia error IIRC, 5100 was their return code for restart required or something? They had some very strange return codes for a while. They are documented somewhere on MSDN, IIRC... but never easy to find. On Wed, Jun 12, 2013 at 3:56 AM, Simon Stevenson redw...@gmail.com wrote: We are getting an error in some cases where we are installing .net 4, and the user is presented with the message Asia. After some investigation it seems that the .net installer is returning exit code 5100, but it is somehow being interpreted as a HRESULT which happens to be the string Asia. Has anyone seen this behaviour or have any idea why this is happening? -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Burn: installer doesn't restart after reboot when variables are specified on cmdline
It appear there's a bug in WiX 3.8 that causes the bootstrapper not to restart installation after a reboot (at least on Server 2003 x64) if variables are specified on the command line. For example if I run: ProductNameSetup.exe /passive The the system will reboot and installation will complete afterwards. However, with: ProductNameSetup.exe /passive DESKTOP_SHORTCUT=0 Where DESKTOP_SHORTCUT is defined as: Variable Name=DESKTOP_SHORTCUT Persisted=yes bal:Overridable=yes/ the system will reboot but the installer doesn't run again. Running it manually causes the progress bar to appear immediately and installation continues, so it seems it's just missing the RunOnce entry to start it after login. -- Bruce Cran -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Suppress options in bundle
Hi all, I am trying to hide the options button on my bundle install as the install folder is fixed and cannot be changed. I am having trouble getting the SuppressOptionUI=yes to work. I am using WiX 3.7 and here is my bundle.wxs from my VS2010 solution. Any help would be greatly appreciated. ?xml version=1.0 encoding=UTF-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Bundle Name=Document Converters Version=$(var.Version) Manufacturer=OmPrompt UpgradeCode=e2e24e5c-5fef-4c16-9b5d-469b67b269a7 Condition=((VersionNT = v5.1) AND (ServicePackLevel = 3)) OR ((VersionNT = v5.2) AND (ServicePackLevel = 2)) OR (VersionNT = v6.0) BootstrapperApplicationRef Id=WixStandardBootstrapperApplication.HyperlinkLicense WixStandardBootstrapperApplication SuppressOptionsUI=yes / /BootstrapperApplicationRef WixVariable Id=WixStdbaLogo Value=Resource\logo.png / WixVariable Id=WixStdbaLicenseUrl Value= / Variable Name=InstallFolder Type=string Value=[ProgramFilesFolder]Omprompt\Document Converters / Variable Name=LaunchTarget Value=[InstallFolder]\ConverterController.exe/ Chain PackageGroupRef Id=NetFx40Redist / RollbackBoundary / MsiPackage Id=WIXConverterInstaller Compressed=yes SourceFile=$(var.WIXConverterInstaller.TargetPath) Vital=yes /MsiPackage /Chain /Bundle /Wix Thanks in advance, Dave Moss -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Suppress options in bundle [P]
Classification: Public Try this: BootstrapperApplicationRef Id=WixExtendedBootstrapperApplication.HyperlinkLicense bal:WixExtendedBootstrapperApplication SuppressRepair=yes SuppressOptionsUI=yes LicenseUrl= /bal:WixExtendedBootstrapperApplication /BootstrapperApplicationRef Steve -Original Message- From: Dave Moss [mailto:davidm...@omprompt.com] Sent: June-13-13 8:16 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Suppress options in bundle Hi all, I am trying to hide the options button on my bundle install as the install folder is fixed and cannot be changed. I am having trouble getting the SuppressOptionUI=yes to work. I am using WiX 3.7 and here is my bundle.wxs from my VS2010 solution. Any help would be greatly appreciated. ?xml version=1.0 encoding=UTF-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Bundle Name=Document Converters Version=$(var.Version) Manufacturer=OmPrompt UpgradeCode=e2e24e5c-5fef-4c16-9b5d-469b67b269a7 Condition=((VersionNT = v5.1) AND (ServicePackLevel = 3)) OR ((VersionNT = v5.2) AND (ServicePackLevel = 2)) OR (VersionNT = v6.0) BootstrapperApplicationRef Id=WixStandardBootstrapperApplication.HyperlinkLicense WixStandardBootstrapperApplication SuppressOptionsUI=yes / /BootstrapperApplicationRef WixVariable Id=WixStdbaLogo Value=Resource\logo.png / WixVariable Id=WixStdbaLicenseUrl Value= / Variable Name=InstallFolder Type=string Value=[ProgramFilesFolder]Omprompt\Document Converters / Variable Name=LaunchTarget Value=[InstallFolder]\ConverterController.exe/ Chain PackageGroupRef Id=NetFx40Redist / RollbackBoundary / MsiPackage Id=WIXConverterInstaller Compressed=yes SourceFile=$(var.WIXConverterInstaller.TargetPath) Vital=yes /MsiPackage /Chain /Bundle /Wix Thanks in advance, Dave Moss -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users This message has been marked as Public by on June-13-13 8:29:51 AM. The above classification labels were added to the message by TITUS Message Classification. For more information visit www.titus.com. -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Suppress options in bundle [P]
Thanks Steve, When I try and build that though I get The BootstrapperApplicationRef element contains an unexpected child element 'bal:WixExtendedBootstrapperApplication'. Dave Moss Tactical Team Lead OmPrompt +44 (0)1235 436014 Direct davidm...@omprompt.com www.omprompt.com OmPrompt Limited is registered in England Wales, registration No. 4452522, with registered offices at 67 Innovation Drive, Milton Park, Abingdon, Oxfordshire. OX14 4RQ. UK. VAT No. 821339546. -Original Message- From: Steven Ogilvie [mailto:steven.ogil...@titus.com] Sent: 13 June 2013 13:30 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Suppress options in bundle [P] Classification: Public Try this: BootstrapperApplicationRef Id=WixExtendedBootstrapperApplication.HyperlinkLicense bal:WixExtendedBootstrapperApplication SuppressRepair=yes SuppressOptionsUI=yes LicenseUrl= /bal:WixExtendedBootstrapperApplication /BootstrapperApplicationRef Steve -Original Message- From: Dave Moss [mailto:davidm...@omprompt.com] Sent: June-13-13 8:16 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Suppress options in bundle Hi all, I am trying to hide the options button on my bundle install as the install folder is fixed and cannot be changed. I am having trouble getting the SuppressOptionUI=yes to work. I am using WiX 3.7 and here is my bundle.wxs from my VS2010 solution. Any help would be greatly appreciated. ?xml version=1.0 encoding=UTF-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Bundle Name=Document Converters Version=$(var.Version) Manufacturer=OmPrompt UpgradeCode=e2e24e5c-5fef-4c16-9b5d-469b67b269a7 Condition=((VersionNT = v5.1) AND (ServicePackLevel = 3)) OR ((VersionNT = v5.2) AND (ServicePackLevel = 2)) OR (VersionNT = v6.0) BootstrapperApplicationRef Id=WixStandardBootstrapperApplication.HyperlinkLicense WixStandardBootstrapperApplication SuppressOptionsUI=yes / /BootstrapperApplicationRef WixVariable Id=WixStdbaLogo Value=Resource\logo.png / WixVariable Id=WixStdbaLicenseUrl Value= / Variable Name=InstallFolder Type=string Value=[ProgramFilesFolder]Omprompt\Document Converters / Variable Name=LaunchTarget Value=[InstallFolder]\ConverterController.exe/ Chain PackageGroupRef Id=NetFx40Redist / RollbackBoundary / MsiPackage Id=WIXConverterInstaller Compressed=yes SourceFile=$(var.WIXConverterInstaller.TargetPath) Vital=yes /MsiPackage /Chain /Bundle /Wix Thanks in advance, Dave Moss -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users This message has been marked as Public by on June-13-13 8:29:51 AM. The above classification labels were added to the message by TITUS Message Classification. For more information visit www.titus.com. -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Suppress options in bundle [P]
Classification: Public Oops using an extended bootstrapper extension my bad, see change: BootstrapperApplicationRef Id=WixStandardBootstrapperApplication.HyperlinkLicense bal:WixStandardBootstrapperApplication SuppressRepair=yes SuppressOptionsUI=yes LicenseUrl= /bal:WixStandardBootstrapperApplication /BootstrapperApplicationRef -Original Message- From: Dave Moss [mailto:davidm...@omprompt.com] Sent: June-13-13 8:59 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Suppress options in bundle [P] Thanks Steve, When I try and build that though I get The BootstrapperApplicationRef element contains an unexpected child element 'bal:WixExtendedBootstrapperApplication'. Dave Moss Tactical Team Lead OmPrompt +44 (0)1235 436014 Direct davidm...@omprompt.com www.omprompt.com OmPrompt Limited is registered in England Wales, registration No. 4452522, with registered offices at 67 Innovation Drive, Milton Park, Abingdon, Oxfordshire. OX14 4RQ. UK. VAT No. 821339546. -Original Message- From: Steven Ogilvie [mailto:steven.ogil...@titus.com] Sent: 13 June 2013 13:30 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Suppress options in bundle [P] Classification: Public Try this: BootstrapperApplicationRef Id=WixExtendedBootstrapperApplication.HyperlinkLicense bal:WixExtendedBootstrapperApplication SuppressRepair=yes SuppressOptionsUI=yes LicenseUrl= /bal:WixExtendedBootstrapperApplication /BootstrapperApplicationRef Steve -Original Message- From: Dave Moss [mailto:davidm...@omprompt.com] Sent: June-13-13 8:16 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Suppress options in bundle Hi all, I am trying to hide the options button on my bundle install as the install folder is fixed and cannot be changed. I am having trouble getting the SuppressOptionUI=yes to work. I am using WiX 3.7 and here is my bundle.wxs from my VS2010 solution. Any help would be greatly appreciated. ?xml version=1.0 encoding=UTF-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Bundle Name=Document Converters Version=$(var.Version) Manufacturer=OmPrompt UpgradeCode=e2e24e5c-5fef-4c16-9b5d-469b67b269a7 Condition=((VersionNT = v5.1) AND (ServicePackLevel = 3)) OR ((VersionNT = v5.2) AND (ServicePackLevel = 2)) OR (VersionNT = v6.0) BootstrapperApplicationRef Id=WixStandardBootstrapperApplication.HyperlinkLicense WixStandardBootstrapperApplication SuppressOptionsUI=yes / /BootstrapperApplicationRef WixVariable Id=WixStdbaLogo Value=Resource\logo.png / WixVariable Id=WixStdbaLicenseUrl Value= / Variable Name=InstallFolder Type=string Value=[ProgramFilesFolder]Omprompt\Document Converters / Variable Name=LaunchTarget Value=[InstallFolder]\ConverterController.exe/ Chain PackageGroupRef Id=NetFx40Redist / RollbackBoundary / MsiPackage Id=WIXConverterInstaller Compressed=yes SourceFile=$(var.WIXConverterInstaller.TargetPath) Vital=yes /MsiPackage /Chain /Bundle /Wix Thanks in advance, Dave Moss -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users This message has been marked as Public by on June-13-13 8:29:51 AM. The above classification labels were added to the message by TITUS Message Classification. For more information visit www.titus.com. -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users This message has been marked as Public by on June-13-13 9:21:29 AM. The above classification labels were added to the message by TITUS Message Classification. For more information visit www.titus.com. -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net
Re: [WiX-users] Can we package html files?
Yes. All but one of my installers supports a web-based WCF service. One of these services also deploys a significant amount of HTML, jScript, and CSS. Payload is payload. -- John Merryweather Cooper Build Install Engineer - ESA Jack Henry Associates, Inc.® Shawnee Mission, KS 66227 Office: 913-341-3434 x791011 jocoo...@jackhenry.com www.jackhenry.com -Original Message- From: Nitin Sharma [mailto:onlynit...@gmail.com] Sent: Thursday, June 13, 2013 1:11 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Can we package html files? Hi Experts, My second day using WiX and I ran into this challenge. I have a bunch of html,css and js files (200+) organized in nested folder structure. Is it possible to use wix for packaging these files and then run this setup on another machine to install the same folder structure and files? Your expert guidance will be much appreciated. -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Suppress options in bundle [P]
Hi Steve, Changed to the updated version and I am now getting The BootstrapperApplicationRef element contains an unhandled extension element 'bal:WixStandardBootstrapperApplication'. Please ensure that the extension for elements in the 'http://schemas.microsoft.com/wix/BalExtension' namespace has been provided. I have a reference in my VS2010 project to WixBalExtension. Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; xmlns:bal=http://schemas.microsoft.com/wix/BalExtension Bundle Name=Document Converters Version=$(var.Version) Manufacturer=OmPrompt UpgradeCode=GUID here Condition=((VersionNT = v5.1) AND (ServicePackLevel = 3)) OR ((VersionNT = v5.2) AND (ServicePackLevel = 2)) OR (VersionNT = v6.0) BootstrapperApplicationRef Id=WixStandardBootstrapperApplication.HyperlinkLicense bal:WixStandardBootstrapperApplication SuppressRepair=yes SuppressOptionsUI=yes LicenseUrl= /bal:WixStandardBootstrapperApplication /BootstrapperApplicationRef Dave Moss Tactical Team Lead OmPrompt +44 (0)1235 436014 Direct davidm...@omprompt.com www.omprompt.com OmPrompt Limited is registered in England Wales, registration No. 4452522, with registered offices at 67 Innovation Drive, Milton Park, Abingdon, Oxfordshire. OX14 4RQ. UK. VAT No. 821339546. -Original Message- From: Steven Ogilvie [mailto:steven.ogil...@titus.com] Sent: 13 June 2013 14:22 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Suppress options in bundle [P] Classification: Public Oops using an extended bootstrapper extension my bad, see change: BootstrapperApplicationRef Id=WixStandardBootstrapperApplication.HyperlinkLicense bal:WixStandardBootstrapperApplication SuppressRepair=yes SuppressOptionsUI=yes LicenseUrl= /bal:WixStandardBootstrapperApplication /BootstrapperApplicationRef -Original Message- From: Dave Moss [mailto:davidm...@omprompt.com] Sent: June-13-13 8:59 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Suppress options in bundle [P] Thanks Steve, When I try and build that though I get The BootstrapperApplicationRef element contains an unexpected child element 'bal:WixExtendedBootstrapperApplication'. Dave Moss Tactical Team Lead OmPrompt +44 (0)1235 436014 Direct davidm...@omprompt.com www.omprompt.com OmPrompt Limited is registered in England Wales, registration No. 4452522, with registered offices at 67 Innovation Drive, Milton Park, Abingdon, Oxfordshire. OX14 4RQ. UK. VAT No. 821339546. -Original Message- From: Steven Ogilvie [mailto:steven.ogil...@titus.com] Sent: 13 June 2013 13:30 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Suppress options in bundle [P] Classification: Public Try this: BootstrapperApplicationRef Id=WixExtendedBootstrapperApplication.HyperlinkLicense bal:WixExtendedBootstrapperApplication SuppressRepair=yes SuppressOptionsUI=yes LicenseUrl= /bal:WixExtendedBootstrapperApplication /BootstrapperApplicationRef Steve -Original Message- From: Dave Moss [mailto:davidm...@omprompt.com] Sent: June-13-13 8:16 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Suppress options in bundle Hi all, I am trying to hide the options button on my bundle install as the install folder is fixed and cannot be changed. I am having trouble getting the SuppressOptionUI=yes to work. I am using WiX 3.7 and here is my bundle.wxs from my VS2010 solution. Any help would be greatly appreciated. ?xml version=1.0 encoding=UTF-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Bundle Name=Document Converters Version=$(var.Version) Manufacturer=OmPrompt UpgradeCode=e2e24e5c-5fef-4c16-9b5d-469b67b269a7 Condition=((VersionNT = v5.1) AND (ServicePackLevel = 3)) OR ((VersionNT = v5.2) AND (ServicePackLevel = 2)) OR (VersionNT = v6.0) BootstrapperApplicationRef Id=WixStandardBootstrapperApplication.HyperlinkLicense WixStandardBootstrapperApplication SuppressOptionsUI=yes / /BootstrapperApplicationRef WixVariable Id=WixStdbaLogo Value=Resource\logo.png / WixVariable Id=WixStdbaLicenseUrl Value= / Variable Name=InstallFolder Type=string Value=[ProgramFilesFolder]Omprompt\Document Converters / Variable Name=LaunchTarget Value=[InstallFolder]\ConverterController.exe/ Chain PackageGroupRef Id=NetFx40Redist / RollbackBoundary / MsiPackage Id=WIXConverterInstaller Compressed=yes SourceFile=$(var.WIXConverterInstaller.TargetPath) Vital=yes /MsiPackage /Chain /Bundle /Wix Thanks in advance, Dave Moss -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___
Re: [WiX-users] Can we package html files?
Hey,thats great news.i kept looking the internet but found nothing that could help.can you please point me to any tutorials.thanks in advance. Nitin On 13-Jun-2013 7:05 PM, John Cooper jocoo...@jackhenry.com wrote: Yes. All but one of my installers supports a web-based WCF service. One of these services also deploys a significant amount of HTML, jScript, and CSS. Payload is payload. -- John Merryweather Cooper Build Install Engineer - ESA Jack Henry Associates, Inc.® Shawnee Mission, KS 66227 Office: 913-341-3434 x791011 jocoo...@jackhenry.com www.jackhenry.com -Original Message- From: Nitin Sharma [mailto:onlynit...@gmail.com] Sent: Thursday, June 13, 2013 1:11 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Can we package html files? Hi Experts, My second day using WiX and I ran into this challenge. I have a bunch of html,css and js files (200+) organized in nested folder structure. Is it possible to use wix for packaging these files and then run this setup on another machine to install the same folder structure and files? Your expert guidance will be much appreciated. -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Suppress options in bundle [P]
Classification: Public Dave Go back to your original code and just modify it to look similar to this: BootstrapperApplicationRef Id=WixStandardBootstrapperApplication.HyperlinkLicense bal:WixStandardBootstrapperApplication SuppressRepair=yes SuppressOptionsUI=yes LicenseUrl= /bal:WixStandardBootstrapperApplication /BootstrapperApplicationRef Keep your application ref, etc.. Steve -Original Message- From: Dave Moss [mailto:davidm...@omprompt.com] Sent: June-13-13 9:42 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Suppress options in bundle [P] Hi Steve, Changed to the updated version and I am now getting The BootstrapperApplicationRef element contains an unhandled extension element 'bal:WixStandardBootstrapperApplication'. Please ensure that the extension for elements in the 'http://schemas.microsoft.com/wix/BalExtension' namespace has been provided. I have a reference in my VS2010 project to WixBalExtension. Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; xmlns:bal=http://schemas.microsoft.com/wix/BalExtension Bundle Name=Document Converters Version=$(var.Version) Manufacturer=OmPrompt UpgradeCode=GUID here Condition=((VersionNT = v5.1) AND (ServicePackLevel = 3)) OR ((VersionNT = v5.2) AND (ServicePackLevel = 2)) OR (VersionNT = v6.0) BootstrapperApplicationRef Id=WixStandardBootstrapperApplication.HyperlinkLicense bal:WixStandardBootstrapperApplication SuppressRepair=yes SuppressOptionsUI=yes LicenseUrl= /bal:WixStandardBootstrapperApplication /BootstrapperApplicationRef Dave Moss Tactical Team Lead OmPrompt +44 (0)1235 436014 Direct davidm...@omprompt.com www.omprompt.com OmPrompt Limited is registered in England Wales, registration No. 4452522, with registered offices at 67 Innovation Drive, Milton Park, Abingdon, Oxfordshire. OX14 4RQ. UK. VAT No. 821339546. -Original Message- From: Steven Ogilvie [mailto:steven.ogil...@titus.com] Sent: 13 June 2013 14:22 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Suppress options in bundle [P] Classification: Public Oops using an extended bootstrapper extension my bad, see change: BootstrapperApplicationRef Id=WixStandardBootstrapperApplication.HyperlinkLicense bal:WixStandardBootstrapperApplication SuppressRepair=yes SuppressOptionsUI=yes LicenseUrl= /bal:WixStandardBootstrapperApplication /BootstrapperApplicationRef -Original Message- From: Dave Moss [mailto:davidm...@omprompt.com] Sent: June-13-13 8:59 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Suppress options in bundle [P] Thanks Steve, When I try and build that though I get The BootstrapperApplicationRef element contains an unexpected child element 'bal:WixExtendedBootstrapperApplication'. Dave Moss Tactical Team Lead OmPrompt +44 (0)1235 436014 Direct davidm...@omprompt.com www.omprompt.com OmPrompt Limited is registered in England Wales, registration No. 4452522, with registered offices at 67 Innovation Drive, Milton Park, Abingdon, Oxfordshire. OX14 4RQ. UK. VAT No. 821339546. -Original Message- From: Steven Ogilvie [mailto:steven.ogil...@titus.com] Sent: 13 June 2013 13:30 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Suppress options in bundle [P] Classification: Public Try this: BootstrapperApplicationRef Id=WixExtendedBootstrapperApplication.HyperlinkLicense bal:WixExtendedBootstrapperApplication SuppressRepair=yes SuppressOptionsUI=yes LicenseUrl= /bal:WixExtendedBootstrapperApplication /BootstrapperApplicationRef Steve -Original Message- From: Dave Moss [mailto:davidm...@omprompt.com] Sent: June-13-13 8:16 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Suppress options in bundle Hi all, I am trying to hide the options button on my bundle install as the install folder is fixed and cannot be changed. I am having trouble getting the SuppressOptionUI=yes to work. I am using WiX 3.7 and here is my bundle.wxs from my VS2010 solution. Any help would be greatly appreciated. ?xml version=1.0 encoding=UTF-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Bundle Name=Document Converters Version=$(var.Version) Manufacturer=OmPrompt UpgradeCode=e2e24e5c-5fef-4c16-9b5d-469b67b269a7 Condition=((VersionNT = v5.1) AND (ServicePackLevel = 3)) OR ((VersionNT = v5.2) AND (ServicePackLevel = 2)) OR (VersionNT = v6.0) BootstrapperApplicationRef Id=WixStandardBootstrapperApplication.HyperlinkLicense WixStandardBootstrapperApplication SuppressOptionsUI=yes / /BootstrapperApplicationRef WixVariable Id=WixStdbaLogo Value=Resource\logo.png / WixVariable Id=WixStdbaLicenseUrl Value= / Variable Name=InstallFolder Type=string
Re: [WiX-users] Can we package html files?
Go here: http://www.wixtoolset.org/ Under documentation there is a book you can buy and/or a link to a tutorial. When I started I got the book. Trying to do it without is painful. The tutorial is pretty good as well. -Original Message- From: Nitin Sharma [mailto:onlynit...@gmail.com] Sent: June-13-13 10:44 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Can we package html files? Hey,thats great news.i kept looking the internet but found nothing that could help.can you please point me to any tutorials.thanks in advance. Nitin On 13-Jun-2013 7:05 PM, John Cooper jocoo...@jackhenry.com wrote: Yes. All but one of my installers supports a web-based WCF service. One of these services also deploys a significant amount of HTML, jScript, and CSS. Payload is payload. -- John Merryweather Cooper Build Install Engineer - ESA Jack Henry Associates, Inc.(r) Shawnee Mission, KS 66227 Office: 913-341-3434 x791011 jocoo...@jackhenry.com www.jackhenry.com -Original Message- From: Nitin Sharma [mailto:onlynit...@gmail.com] Sent: Thursday, June 13, 2013 1:11 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Can we package html files? Hi Experts, My second day using WiX and I ran into this challenge. I have a bunch of html,css and js files (200+) organized in nested folder structure. Is it possible to use wix for packaging these files and then run this setup on another machine to install the same folder structure and files? Your expert guidance will be much appreciated. -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] help controlling uninstall bundle behavior
I need some help finding a good behavior for uninstalling using bundles.
My bundle installs 4 things (wxs at end of this message):
Two ExePackage,
Two MsiPackage
From Control Panel-Programs and Features,
I see an entry for each item in my chain, which I like.
I also see multiple entries for my bundle, which I don't like as it
could confuse the users.
Additionally, Uninstalling the bundle does not uninstall the items in
the chain, it simply removes the bundle from Control Panel-Programs
and Features which seems like busy work.
My ignorant view, and please correct me if I'm wrong, thinks users will
be confused by seeing bundle in Control Panel-Programs and
Features, in addition to the chained packages, so maybe it should not
be there, as it has no functional purpose.
I see two Bundle attributes:
DisableModify
DisableRemove
which seem to address hiding my bundle in Control Panel-Programs and
Features, but not cleanly?
http://wix.sourceforge.net/manual-wix3/wix_xsd_bundle.htm
says I just find some other way to clean out my bundle, but no examples
given.
Has anyone found a nice recipe for dealing with bundles?
My Wxs for the Bundle follows:
?xml version=1.0 encoding=UTF-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
xmlns:bal=http://schemas.microsoft.com/wix/BalExtension;
xmlns:util=http://schemas.microsoft.com/wix/UtilExtension;
Bundle
Name=$(var.BundleExe)
Version=1.0.0.0
Manufacturer=$(var.MyCompanyName)
Copyright=(c) All rights reserved.
UpgradeCode={$(var.Guid_Bundle)}
HelpTelephone=1 234 567 8910
HelpUrl=https://mycopany.com/software/compass?section=support;
UpdateUrl=https://mycompany.com/software/compass?section=download;
AboutUrl=https://mycompany.com/software/compass?section=overview;
SplashScreenSourceFile=../ProgramFiles/Resources/Images/InstallerHeaderImage.bmp
!-- Display License and Logo --
BootstrapperApplicationRef
Id=WixStandardBootstrapperApplication.HyperlinkLicense
bal:WixStandardBootstrapperApplication
LicenseUrl=https://www.meyersound.com/software/compass?section=download;
LogoFile=../Source/Resources/Images/AboutCompass.png
/
/BootstrapperApplicationRef
!-- BEGIN Conditional Def --
!-- Check if WinPcap is installed and at least some version --
util:RegistrySearch
Id=RegistrySearchWinPcapHas
Variable=WinPcapInstalled
Root=HKLM
Key=SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
\WinPcapInst
Result=exists
/
util:RegistrySearch
Id=RegistrySearchWinPcapMajor
Variable=WinPcapVersionMajor
Root=HKLM
Key=SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
\WinPcapInst
Value=VersionMajor
Format=raw
Result=value
/
util:RegistrySearch
Id=RegistrySearchWinPcapMinor
Variable=WinPcapVersionMinor
Root=HKLM
Key=SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
\WinPcapInst
Value=VersionMinor
Format=raw
Result=value
/
!-- Check if Bounjour Print Services is installed --
util:RegistrySearch
Id=RegistrySearchBonjourHas
Variable=BonjourDLL
Root=HKLM
Key=SOFTWARE\Classes\AppID\Bonjour.DLL
Result=exists
/
util:RegistrySearch
Id=RegistrySearchBonjourValue
Variable=BounjourVersion
Root=HKLM
Key=SOFTWARE\Apple Inc.\Bonjour
Value=Version
Format=raw
Result=value
/
!-- Check if Avdeccproxy is installed and at least some version --
util:RegistrySearch
Id=RegistrySearchProxyHas
Variable=ProxyInstalled
Root=HKLM
Key=SOFTWARE\Meyer Sound\AVDECC Proxy
Result=exists
/
!-- END Conditional Def --
!-- Begin Chain --
Chain
!-- Will not install if 4.1.3 or better is installed --
ExePackage
Id=WinPcap
Name=WinPcap_4_1_3.exe
Vital=no
Compressed=no
DownloadUrl=http://www.winpcap.org/install/bin/WinPcap_4_1_3.exe;
InstallCondition=NOT WinPcapInstalled OR ( 4
WinPcapVersionMajor AND 1 WinPcapVersionMinor)
RemotePayload
Description=WinPcap 4.1.3 installer
Hash=e2516fcd1573e70334c8f50bee5241cdfdf48a00
ProductName=WinPcap 4.1.3
Size=915128
Version=4.1.0.2980
/
/ExePackage
!-- Will not install if 2.0.2.0 or better is installed --
ExePackage
Id=BonjourPSSetup
Name=BonjourPSSetup.exe
Vital=no
Compressed=no
DownloadUrl=http://support.apple.com/downloads/DL999/en_US/BonjourPSSetup.exe;
InstallCondition=NOT BonjourDLL OR v2.0.2.0 BonjourVersion
RemotePayload
ProductName=BonjourPrintServices
Description=Bonjour Printer Services Installer
Size=5436744
Version=2.0.2.0
Hash=847f39e0ea80d2a4d902fe59657e18f5bc32a8cb
/
/ExePackage
!-- Will not
Re: [WiX-users] [nik] Issue with Burn installer
I am starting to wonder if the way I am trying to use Burn might be the issue.
I am trying to provide a single installer that will install that includes a
32bit and a 64bit MSI and will install the correct version. There are no
related packages.
Nik Twerdochlib
Software Developer
-Original Message-
From: Nik Twerdochlib
Sent: Thursday, June 13, 2013 1:47 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] [nik] Issue with Burn installer
I have an installer that uses Burn. If I rebuild the installer without
changing any content and then run that installer it will install another
version alongside an existing one?
Using the individual MSI installers there is no issue with upgrades. This only
occurs when running the burn installer that has been rebuilt. Does anyone know
why this occurs and what can be done to fix it?
I have read that burn should first uninstall a current version then reinstall,
but I do not see this occurring. Log from the burn installer:
[2DF0:1360][2013-06-13T00:30:48]i001: Burn v3.7.1611.0, Windows v6.1 (Build
7601: Service Pack 1), path: elvsvc.exe, cmdline: '/log ib.log'
[2DF0:1360][2013-06-13T00:30:48]i000: Initializing string variable 'DISPLAYVER'
to value '1.0.1'
[2DF0:1360][2013-06-13T00:30:48]i000: Initializing string variable 'VERSION' to
value '1.0.1.1'
[2DF0:1360][2013-06-13T00:30:48]i000: Setting string variable 'WixBundleLog' to
value 'ib.log'
[2DF0:1360][2013-06-13T00:30:48]i000: Setting string variable
'WixBundleOriginalSource' to value 'elvsvc.exe'
[2DF0:1360][2013-06-13T00:30:48]i052: Condition 'VersionNT = v5.1' evaluates
to true.
[2DF0:1360][2013-06-13T00:30:48]i000: Setting string variable 'WixBundleName'
to value 'Test'
[2DF0:1360][2013-06-13T00:30:48]i100: Detect begin, 2 packages
[2DF0:1360][2013-06-13T00:30:48]i102: Detected related bundle:
{8eeeb531-9a26-48f5-a1f7-d6a59e05ef06}, type: Upgrade, scope: PerMachine,
version: 1.0.1.1, operation: None
[2DF0:1360][2013-06-13T00:30:48]i103: Detected related package:
{2F852825-CDDA-4FC4-B0D3-ABC4660BB139}, scope: PerMachine, version: 1.0.1.1,
language: 0 operation: MajorUpgrade
[2DF0:1360][2013-06-13T00:30:48]i101: Detected package: ElvSvc32, state:
Absent, cached: None
[2DF0:1360][2013-06-13T00:30:48]i101: Detected package: ElvSvc64, state:
Present, cached: Complete
[2DF0:1360][2013-06-13T00:30:48]i199: Detect complete, result: 0x0
[2DF0:1360][2013-06-13T00:30:55]i200: Plan begin, 2 packages, action: Install
[2DF0:1360][2013-06-13T00:30:55]i052: Condition '(NOT VersionNT64)' evaluates
to false.
[2DF0:1360][2013-06-13T00:30:55]i052: Condition 'VersionNT64' evaluates to true.
[2DF0:1360][2013-06-13T00:30:55]i201: Planned package: ElvSvc32, state: Absent,
default requested: Absent, ba requested: Absent, execute: None, rollback: None,
cache: No, uncache: No, dependency: None
[2DF0:1360][2013-06-13T00:30:55]i201: Planned package: ElvSvc64, state:
Present, default requested: Present, ba requested: Present, execute: None,
rollback: None, cache: No, uncache: No, dependency: Register
[2DF0:1360][2013-06-13T00:30:55]i207: Planned related bundle:
{8eeeb531-9a26-48f5-a1f7-d6a59e05ef06}, type: Upgrade, default requested: None,
ba requested: None, execute: None, rollback: None, dependency: None
[2DF0:1360][2013-06-13T00:30:55]i299: Plan complete, result: 0x0
[2DF0:1360][2013-06-13T00:30:55]i300: Apply begin
[2FA4:29FC][2013-06-13T00:30:58]i360: Creating a system restore point.
[2FA4:29FC][2013-06-13T00:31:03]i361: Created a system restore point.
[2FA4:29FC][2013-06-13T00:31:04]i000: Caching bundle from:
'C:\Users\NTWERD~1\AppData\Local\Temp\{f55ab761-afb5-4e7f-a790-0427ec346d25}\.be\bundle.exe'
to: 'C:\ProgramData\Package
Cache\{f55ab761-afb5-4e7f-a790-0427ec346d25}\bundle.exe'
[2FA4:29FC][2013-06-13T00:31:04]i320: Registering bundle dependency provider:
{f55ab761-afb5-4e7f-a790-0427ec346d25}, version: 1.0.1.1
[2FA4:29FC][2013-06-13T00:31:04]i323: Registering package dependency provider:
{2F852825-CDDA-4FC4-B0D3-ABC4660BB139}, version: 1.0.1.1, package: ElvSvc64
[2FA4:29FC][2013-06-13T00:31:04]i325: Registering dependency:
{f55ab761-afb5-4e7f-a790-0427ec346d25} on package provider:
{2F852825-CDDA-4FC4-B0D3-ABC4660BB139}, package: ElvSvc64
[2DF0:1360][2013-06-13T00:31:04]i399: Apply complete, result: 0x0, restart:
None, ba requested restart: No
[2DF0:1360][2013-06-13T00:31:07]i500: Shutting down, exit code: 0x0
[2DF0:1360][2013-06-13T00:31:07]i410: Variable: DISPLAYVER = 1.0.1
[2DF0:1360][2013-06-13T00:31:07]i410: Variable: VERSION = 1.0.1.1
[2DF0:1360][2013-06-13T00:31:07]i410: Variable: VersionNT = 6.1.0.0
[2DF0:1360][2013-06-13T00:31:07]i410: Variable: VersionNT64 = 6.1.0.0
[2DF0:1360][2013-06-13T00:31:07]i410: Variable: WixBundleAction = 4
[2DF0:1360][2013-06-13T00:31:07]i410: Variable: WixBundleElevated = 1
[2DF0:1360][2013-06-13T00:31:07]i410: Variable: WixBundleInstalled = 0
[2DF0:1360][2013-06-13T00:31:07]i410: Variable: WixBundleLog = ib.log
Re: [WiX-users] [nik] Issue with Burn installer
You need to increment the version of the bundle every time you build it (and
deploy it). Also, what is the intent behind the RelatedBundle elements? Having
a bundle related to itself and set to upgrade just seems wrong to me.
-Original Message-
From: Nik Twerdochlib [mailto:ntwerdoch...@bomgar.com]
Sent: Thursday, June 13, 2013 1:12 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] [nik] Issue with Burn installer
I am starting to wonder if the way I am trying to use Burn might be the issue.
I am trying to provide a single installer that will install that includes a
32bit and a 64bit MSI and will install the correct version. There are no
related packages.
Nik Twerdochlib
Software Developer
-Original Message-
From: Nik Twerdochlib
Sent: Thursday, June 13, 2013 1:47 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] [nik] Issue with Burn installer
I have an installer that uses Burn. If I rebuild the installer without
changing any content and then run that installer it will install another
version alongside an existing one?
Using the individual MSI installers there is no issue with upgrades. This only
occurs when running the burn installer that has been rebuilt. Does anyone know
why this occurs and what can be done to fix it?
I have read that burn should first uninstall a current version then reinstall,
but I do not see this occurring. Log from the burn installer:
[2DF0:1360][2013-06-13T00:30:48]i001: Burn v3.7.1611.0, Windows v6.1 (Build
7601: Service Pack 1), path: elvsvc.exe, cmdline: '/log ib.log'
[2DF0:1360][2013-06-13T00:30:48]i000: Initializing string variable 'DISPLAYVER'
to value '1.0.1'
[2DF0:1360][2013-06-13T00:30:48]i000: Initializing string variable 'VERSION' to
value '1.0.1.1'
[2DF0:1360][2013-06-13T00:30:48]i000: Setting string variable 'WixBundleLog' to
value 'ib.log'
[2DF0:1360][2013-06-13T00:30:48]i000: Setting string variable
'WixBundleOriginalSource' to value 'elvsvc.exe'
[2DF0:1360][2013-06-13T00:30:48]i052: Condition 'VersionNT = v5.1' evaluates
to true.
[2DF0:1360][2013-06-13T00:30:48]i000: Setting string variable 'WixBundleName'
to value 'Test'
[2DF0:1360][2013-06-13T00:30:48]i100: Detect begin, 2 packages
[2DF0:1360][2013-06-13T00:30:48]i102: Detected related bundle:
{8eeeb531-9a26-48f5-a1f7-d6a59e05ef06}, type: Upgrade, scope: PerMachine,
version: 1.0.1.1, operation: None
[2DF0:1360][2013-06-13T00:30:48]i103: Detected related package:
{2F852825-CDDA-4FC4-B0D3-ABC4660BB139}, scope: PerMachine, version: 1.0.1.1,
language: 0 operation: MajorUpgrade
[2DF0:1360][2013-06-13T00:30:48]i101: Detected package: ElvSvc32, state:
Absent, cached: None
[2DF0:1360][2013-06-13T00:30:48]i101: Detected package: ElvSvc64, state:
Present, cached: Complete
[2DF0:1360][2013-06-13T00:30:48]i199: Detect complete, result: 0x0
[2DF0:1360][2013-06-13T00:30:55]i200: Plan begin, 2 packages, action: Install
[2DF0:1360][2013-06-13T00:30:55]i052: Condition '(NOT VersionNT64)' evaluates
to false.
[2DF0:1360][2013-06-13T00:30:55]i052: Condition 'VersionNT64' evaluates to true.
[2DF0:1360][2013-06-13T00:30:55]i201: Planned package: ElvSvc32, state: Absent,
default requested: Absent, ba requested: Absent, execute: None, rollback: None,
cache: No, uncache: No, dependency: None
[2DF0:1360][2013-06-13T00:30:55]i201: Planned package: ElvSvc64, state:
Present, default requested: Present, ba requested: Present, execute: None,
rollback: None, cache: No, uncache: No, dependency: Register
[2DF0:1360][2013-06-13T00:30:55]i207: Planned related bundle:
{8eeeb531-9a26-48f5-a1f7-d6a59e05ef06}, type: Upgrade, default requested: None,
ba requested: None, execute: None, rollback: None, dependency: None
[2DF0:1360][2013-06-13T00:30:55]i299: Plan complete, result: 0x0
[2DF0:1360][2013-06-13T00:30:55]i300: Apply begin
[2FA4:29FC][2013-06-13T00:30:58]i360: Creating a system restore point.
[2FA4:29FC][2013-06-13T00:31:03]i361: Created a system restore point.
[2FA4:29FC][2013-06-13T00:31:04]i000: Caching bundle from:
'C:\Users\NTWERD~1\AppData\Local\Temp\{f55ab761-afb5-4e7f-a790-0427ec346d25}\.be\bundle.exe'
to: 'C:\ProgramData\Package
Cache\{f55ab761-afb5-4e7f-a790-0427ec346d25}\bundle.exe'
[2FA4:29FC][2013-06-13T00:31:04]i320: Registering bundle dependency provider:
{f55ab761-afb5-4e7f-a790-0427ec346d25}, version: 1.0.1.1
[2FA4:29FC][2013-06-13T00:31:04]i323: Registering package dependency provider:
{2F852825-CDDA-4FC4-B0D3-ABC4660BB139}, version: 1.0.1.1, package: ElvSvc64
[2FA4:29FC][2013-06-13T00:31:04]i325: Registering dependency:
{f55ab761-afb5-4e7f-a790-0427ec346d25} on package provider:
{2F852825-CDDA-4FC4-B0D3-ABC4660BB139}, package: ElvSvc64
[2DF0:1360][2013-06-13T00:31:04]i399: Apply complete, result: 0x0, restart:
None, ba requested restart: No
[2DF0:1360][2013-06-13T00:31:07]i500: Shutting down, exit code: 0x0
[2DF0:1360][2013-06-13T00:31:07]i410: Variable: DISPLAYVER = 1.0.1
[2DF0:1360][2013-06-13T00:31:07]i410:
Re: [WiX-users] Read an Installed software Path from Registry update in Registry
You need something like this example of RegistrySearch that sets a property: http://wix.sourceforge.net/manual-wix3/read_a_registry_entry.htm You'll need a custom action to read that property, add your data creating another propertyb that you can then write to the registry with a RegistryValue element: http://wix.sourceforge.net/manual-wix3/wix_xsd_registryvalue.htm I don't think WiX has built-in support for doing Path.Combine() types of actions, and MSI doesn't. Phil -Original Message- From: Chaitanya [mailto:chaita...@pointcross.com] Sent: Thursday, June 13, 2013 12:32 AM To: WiX-users@lists.sourceforge.net Subject: [WiX-users] Read an Installed software Path from Registry update in Registry hi, I need to read an Apache Software installed path from Registry.i need to update that path in my main registry Any suggestions Acceptable. Thanks Regrds, chaitanya. -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Patching error
I following online instructions and created a patch (msp file). There were no
errors during the creation. When I tried to verify the patch by applying it, I
got following error:
MSI (s) (C0:F0) [13:36:29:463]: Executing op: ActionStart(Name=CreateUser,,)
MSI (s) (C0:F0) [13:36:29:463]: Executing op:
CustomActionSchedule(Action=CreateUser,ActionType=11265,Source=BinaryData,Target=**,CustomActionData=**)
MSI (s) (C0:88) [13:36:29:463]: Invoking remote custom action. DLL:
C:\Windows\Installer\MSIA410.tmp, Entrypoint: CreateUser
MSI (s) (C0:9C) [13:36:29:463]: Generating random cookie.
MSI (s) (C0:9C) [13:36:29:463]: Created Custom Action Server with PID 3760
(0xEB0).
MSI (s) (C0:A8) [13:36:29:495]: Running as a service.
MSI (s) (C0:FC) [13:36:29:495]: Hello, I'm your 32bit Elevated custom action
server.
CreateUser: Error 0x80070103: failed to read attributes from custom action data
CustomAction CreateUser returned actual error code 1603 (note this may not be
100% accurate if translation happened inside sandbox)
Action ended 13:36:29: InstallFinalize. Return value 3.
My code that has CreateUser in it is:
Component Id='' Win64=$(var.Win64)
Guid='{*}'
util:User Id='***' Name='[SERVICEACCOUNT]'
Password='[SERVICEPASSWORD]' CreateUser='no' LogonAsService='yes'/
File Id=*** Name=** KeyPath=yes
Source=* /
ServiceInstall Id='*'
Name='**'
DisplayName='***'
Type='ownProcess'
Start='auto'
ErrorControl='normal'
Description='**'
Account='[SERVICEACCOUNT]'
Password='[SERVICEPASSWORD]'
Vital='yes'
util:ServiceConfig FirstFailureActionType='restart'
SecondFailureActionType='restart' ThirdFailureActionType='none'
RestartServiceDelayInSeconds='10'
ResetPeriodInDays='1'/
/ServiceInstall
ServiceControl Id=StartService Stop=both Remove=uninstall
Name=** Wait=yes /
/Component
I am a bit at loss as to how to fix this problem. I have heard that when
patching, custom actions lose their parameters. Is this true? If util:user is
internally implemented as a custom action, how do I get around this?
Thanks,
George
--
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
