You'd need to use a bootstrapper for that. Until Burn is done WiX doesn't have any support for this. I would recommend dotnetinstaller (http://dotnetinstaller.codeplex.com/) but other bootstrappers are widely available.
Palbinder Sandher Software Deployment & IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the <Virtual Environment>** 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: Sanjay Rao [mailto:s...@noida.interrasystems.com] Sent: 07 July 2010 14:02 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] wix installer is very slow. -I changes product code everytime. I do not changes upgradecode. after splitting it into two msi files is there any way to combine them into single file, so that user do not need to download two files and install them separately. suppose I have two msi files 1. constant.msi 2. variable.msi I want to make a single file containing these two, which detects whether constant.msi installed or not. - if yes, do not install constant.msi. install variable.msi only. - if no install both msi files. Pally Sandher wrote: > This is a known issue with *Windows Installer* patching & upgrades. > Windows Installer & WiX are not the same thing. > I'm guessing you're using Major Upgrades to upgrade (correct me if I'm > wrong). Take a look at a verbose log when upgrading or uninstalling & > see where it's taking so long. My guess will be between CostInitialize > & CostFinalize since it checks what is installed before it does anything. > > - I want make this time down to around 10-15 minutes. What are > possible schemes for that ? > > Install fewer files. > A couple of years ago I separated our company's main product into 2 > MSI's, one installs most of the files (5000+, approx 1 GB installed) > but changes very very rarely. The other installs the actual > application binaries & other things which change with each release > (1600+ files, 220 MB installed). This makes patching & upgrading work > much faster since there are a lot less things for Windows Installer to > have to check every time a user runs a patch or upgrade. > > - Is there any mechanism to define force upgrade for each component ? > > What do you mean by "force upgrade"? Major Upgrades can force every > component to be reinstalled regardless of the current state if you > schedule RemoveExistingProducts before InstallInitialize rather than > after but this brings additional considerations with regards to the > Component Rules. > > Palbinder Sandher > Software Deployment & IT Administrator > T: +44 (0) 141 945 8500 > F: +44 (0) 141 945 8501 > > http://www.iesve.com > **Design, Simulate + Innovate with the <Virtual Environment>** > 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: Sanjay Rao [mailto:s...@noida.interrasystems.com] > Sent: 07 July 2010 11:20 > To: General discussion for Windows Installer XML toolset. > Subject: [WiX-users] wix installer is very slow. > > Hi All, > > I have a installer which installs large number of files(~50000 files). > It takes a lot of time to install. However it's installation time is > tolerable. > But while upgrading it takes intolerable amount of time(more than 1 > hour sometimes). It also takes lot of time(1 hour) in un installation. > > - I want make this time down to around 10-15 minutes. What are > possible schemes for that ? > - Is there any mechanism to define force upgrade for each component ? > > Regards, > Sanjay Rao > > > > ---------------------------------------------------------------------- > -- > ------ > This SF.net email is sponsored by Sprint What will you do first with > EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > ---------------------------------------------------------------------- > -------- This SF.net email is sponsored by Sprint What will you do > first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > ------------------------------------------------------------------------ ------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
