Hi: 
Ok, that makes sense. How do I go about populating the directory I want to 
install to based on the platform I'm installing on?
My msi has stuff installed in to %program files% and %ProgramData% and has 
several defines for 32/64-bit.
I'm quite happy to send the msi/compiled code.
Any help appreciated.
Cheers
Sean.


-----Original Message-----
From: Rob Mensching [mailto:r...@robmensching.com] 
Sent: 03 July 2012 04:36
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] using the internal msi ui

Your MSI UI shows up during the Apply() phase. Apply happens after you click 
the Install button in the wixstdba.

On Mon, Jul 2, 2012 at 7:54 PM, Sean Farrow <sean.far...@seanfarrow.co.uk>wrote:

> Hi Fokes:
> I'm just in the process of preparing a bundle with burn (the latest 
> weekly release).
> My bundle markup looks as follows:
> <?xml version="1.0" encoding="UTF-8"?> <Wix 
> xmlns="http://schemas.microsoft.com/wix/2006/wi";>
>   <?define SRWorkingDirectory = "c:\work\" ?>
>   <Bundle Name="SurfaceReaderInstaller" Version="1.0.0.0"
> Manufacturer="Raised Bar"
> UpgradeCode="BE7E0AAB-A663-4B16-904C-0BCC718BEA6D">
>                                 <BootstrapperApplicationRef 
> Id="WixStandardBootstrapperApplication.RtfLicense" />
>
>                                 <Chain>
>                                                 <!-- TODO: Define the 
> list of chained packages. -->
>       <MsiPackage SourceFile="$(var.Installer Msi x86.TargetPath)"
> Compressed="yes" DisplayInternalUI="yes" InstallCondition="VersionNT
> >=v5.1"/>
>       <MsiPackage
> SourceFile="$(var.SRWorkingDirectory)srrt54\Windows\Installer
> MSI\bin\x64\$(var.Configuration)\SurfaceReader64.msi" Compressed="yes"
> DisplayInternalUI="yes" InstallCondition="VersionNT64 >=v6.0"/>
>                                 </Chain>
>                 </Bundle>
> </Wix>
> With this markup I'd expect to see the internal ui of the msi (which 
> ever one is run depending on the system). However I see the 
> bootstrapper ui interface.
> Is this correct behaviour, and if so how do I get my internal msi ui shown?
> Any help appreciated as this is for an iminant product release.
> Cheers
> Sean.
>
> ----------------------------------------------------------------------
> --------
> 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

Reply via email to