1. There is a bug in rollback handling of Burn. DisableRollback="yes" will cause Burn to not rollback (but leave all your packages on the machine if there is a failure/cancel). <smile/> The bug will get fixed.
2. When installing NETFX 4, I suggest setting ExePackage/@Protocol="netfx" and you'll get progress pumped through the Burn engine rather than having NETFX UI show up. 4. Burn pipes all the MSI UI through the engine so you get unified progress and also controls the reboot behavior to ensure Burn gets a chance to clean-up and shutdown correctly. Burn actually does a lot to handle all the reboot handling for you. Recen builds even suppress Windows shutdown while the install is continuing so users don't accidentally shutdown with an install partially executing (of course, they can always force the shutdown given the way Windows handles shutdown). On Tue, Aug 23, 2011 at 11:31 AM, Tobias S <tobias.s1...@gmail.com> wrote: > > <Chain DisableRollback="no" ParallelCache="no"> > DisableRollback="no" > Think somewhere here in the list it was mentioned a reason for use Yes > here due beta behavior of burn > > > <ExePackage Id="DotNet4" > > InstallCommand="/q /norestart" > SourceFile="c:\portal_bundles\dotNetFx40_Full_setup.exe" > Name="c:\pediatric_oncology_portal\dotNet4" Permanent="no" Compressed="no" > Cache="no"></ExePackage> > > See src\Setup\Bundle\Netfx.wxs in Wix 3.6 sources for a sample > implementation of netfx4 full > Permanent="yes" (as netFx would cause trouble if beeing uninstalled) > InstallCommand="/passive /promptrestart" I used for a sample > implementation. Passive to have progress for customer (think maybe a > future implementation of burn might catch the FW progress) and restart > to force restarting in passive mode. (Personal preferences) See > http://msdn.microsoft.com/en-us/library/ee942965.aspx for deployment > guide > > > > <ExePackage Id="WicENU" > > InstallCommand="/q /norestart" > SourceFile="c:\portal_bundles\wic_x86_enu.exe" > Name="c:\pediatric_oncology_portal\wic" Compressed="no" > Cache="no"></ExePackage> > packages are installed in the order they are defined her. Windows > Imaging component slould be before netFx4. Additionally I mean when > you're deploying xp SP2 consider missing MSI 3.1 which i think is > needed for netFx4 > > > > <MsiPackage Id="Imprivata" > > > SourceFile="c:\portal_bundles\Imprivata_With_Susp_Res.msi \qn > \forcerestart" Name="c:\pediatric_oncology_portal\" Compressed="no" > EnableFeatureSelection="no" > > /qn is default handling of burn. Think there exist no other possibility for > MSIs > /forcerestart:not absolutely sure about: Think burn handles that as > well, but not 100% sure. Also no sure about but try <MsiProperty > Name="REBOOT" Value="force"/> which should be same. > > > ------------------------------------------------------------------------------ > Get a FREE DOWNLOAD! and learn more about uberSVN rich system, > user administration capabilities and model configuration. Take > the hassle out of deploying and managing Subversion and the > tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2 > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- virtually, Rob Mensching - http://RobMensching.com LLC ------------------------------------------------------------------------------ EMC VNX: the world's simplest storage, starting under $10K The only unified storage solution that offers unified management Up to 160% more powerful than alternatives and 25% more efficient. Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
