Re: [WiX-users] Issues when writing an installer using burn
The problem is that you're missing an install condition for the x86 version of
your MSI so burn is trying to install it after having already installed the x64
version. Add an install condition to the MsiPackage element for the x86 package
saying 'NOT VersionNT64' to make it's not installed on 64 bit platforms,
Sent from my iPhone
On 11 Jul 2012, at 06:05, "wix-users-requ...@lists.sourceforge.net"
wrote:
> Send WiX-users mailing list submissions to
>wix-users@lists.sourceforge.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
>https://lists.sourceforge.net/lists/listinfo/wix-users
> or, via email, send a message with subject or body 'help' to
>wix-users-requ...@lists.sourceforge.net
>
> You can reach the person managing the list at
>wix-users-ow...@lists.sourceforge.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of WiX-users digest..."
>
>
> Today's Topics:
>
> 1. Re: Issues when writing an installer using burn (Sean Farrow)
> 2. Re: Issues when writing an installer using burn (Rob Mensching)
>
>
> --
>
> Message: 1
> Date: Wed, 11 Jul 2012 04:41:01 +0100
> From: Sean Farrow
> Subject: Re: [WiX-users] Issues when writing an installer using burn
> To: General discussion for Windows Installer XML toolset.
>
> Message-ID:
><95bc1059fb290d48835f2531a70ecb9a726c7f3...@ex27mail03.msghub.com>
> Content-Type: text/plain; charset="us-ascii"
>
> 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]: Regis
Re: [WiX-users] How to do offline install of WiX 3.6 RC?
Run the setup executable with the /layout command on a machine that does have connectivity. It should download all required files into a folder of your choosing. Copy that to your target machine then rerun setup as normal. Sent from my iPhone On 14 Jul 2012, at 04:23, "wix-users-requ...@lists.sourceforge.net" wrote: > Re: [WiX-users] How to do offline install of WiX 3.6 RC? -- 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] Heat and Recursion
Is there a way to tell heat not to recurse through a directory tree but to only harvest the top-level files? Sent from my iPhone On 6 Sep 2012, at 09:13, "wix-users-requ...@lists.sourceforge.net" wrote: > Send WiX-users mailing list submissions to >wix-users@lists.sourceforge.net > > To subscribe or unsubscribe via the World Wide Web, visit >https://lists.sourceforge.net/lists/listinfo/wix-users > or, via email, send a message with subject or body 'help' to >wix-users-requ...@lists.sourceforge.net > > You can reach the person managing the list at >wix-users-ow...@lists.sourceforge.net > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of WiX-users digest..." > > > Today's Topics: > > 1. Re: Running an Exe (Hoover, Jacob) > 2. MsiPackage - Uninstall After (Adam Westhusing) > 3. Re: MsiPackage - Uninstall After (Rob Mensching) > 4. Re: modify CheckBox control (Ingo Fischer) > 5. Re: Running an Exe (Natalie Carr) > > > -- > > Message: 1 > Date: Wed, 5 Sep 2012 21:58:06 + > From: "Hoover, Jacob" > Subject: Re: [WiX-users] Running an Exe > To: "chr...@iswix.com" , "General discussion for >WindowsInstaller XML toolset." > Message-ID: ><61d0a1ed0452f744bd7fe991abc2196f039...@exbox2.greenops.com> > Content-Type: text/plain; charset="us-ascii" > > Natalie, > It is not recommended to do concurrent installs with a pure MSI based > approach > (http://msdn.microsoft.com/en-us/library/windows/desktop/aa368010(v=vs.85).aspx). > Either it has to be transformed into a merge module and thus a single > install, or you need to generate a Burn bundle (or you could try another boot > strapping application or write your own). If you don't heed this advice you > are going to run into many problems and since it's unsupported you would be > on your own to try to hack in fixes if they are even possible. > > Stripping out the UI from your MSI and putting it into a Burn based managed > UX should be fairly easy to do. Then you could simply pass in any additional > information you got in your UI as properties to your now UI less MSI. > > If this executable isn't a prerequisite in order for your application to > run, you could also (conditionally) execute the exe after your install has > completed. > > Jacob > > > -Original Message- > From: Christopher Painter [mailto:chr...@iswix.com] > Sent: Wednesday, September 05, 2012 3:30 PM > To: General discussion for Windows Installer XML toolset.; General discussion > for Windows Installer XML toolset. > Subject: Re: [WiX-users] Running an Exe > > There is a mutex to prevent multiple execute sequences. If you are doing > some kind of hack in MSI then you need to do it all from the UI sequence of > the parent installer. If you want that parent to ever work silently the > closest you'll get is 'non-interactive' using /qr. > > You didn't seem to 'like' Pally's answer. Well, to be honest, it is the > right answer. You are in unsupported territory so you'll have to get your > big boy pants on and figure it out yourself. I've been there, there are many > gotchas to watch out for. > > Good luck. > > > From: "Natalie Carr" > Sent: Wednesday, September 05, 2012 5:52 AM > To: "General discussion for Windows Installer XML toolset." > > Subject: Re: [WiX-users] Running an Exe > > Hi, Thanks, I don't want to use Burn as I have spent a great deal of time > making my own dialog set to cater for our needs and I do not like the way if > you display your own MSI dialogs it still shows the Burn dialog. Thanks for > your answer though..:) > > -Original Message- > From: Pally Sandher [mailto:pally.sand...@iesve.com] > Sent: 05 September 2012 11:04 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Running an Exe > > This is what you're doing wrong -> > http://msdn.microsoft.com/en-us/library/windows/desktop/bb204770.aspx#concur > > rent_installs > > This is how you fix it -> > http://wix.sourceforge.net/manual-wix3/authoring_bundle_intro.htm > > Palbinder Sandher > Software Platform Engineer > T: +44 (0) 141 945 8500 > F: +44 (0) 141 945 8501 > http://www.iesve.com > > **Design, Simulate + Innovate with the ** Integrated > Environmental Solutions Limited. Registered in Scotland No. SC151456 > Registered Office - Helix Building, West Of Scotland Science Park, Glasgow > G20 0SP Email Disclaimer > > -Original Message- > From: Natalie Carr [mailto:natalie.c...@measuresoft.com] > Sent: 04 September 2012 16:01 > To: wix-users@lists.sourceforge.net > Subject: [WiX-users] Running an Exe > > I'm trying to run an exe when a user clicks a button, can anyone please tell > me what i am doing wrong or tell me how to do it please. Thanks > > > > ExeCommand="sentinel_setup.exe" Execute="immediate" Retu
