--
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christopher
Painter
Sent: Tuesday, May 20, 2008 8:51 AM
To: Ene Stelian-Bogdan; Rob Mensching; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Integrate WiX in our process
I'd like to address
ian-Bogdan; Rob Mensching; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Integrate WiX in our process
I'd like to address a couple things about InstallShield.In IS2009
(currently Beta) there is improved support for dynamic linking and
upgrading/patching support. Things like
--
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christopher
Painter
Sent: Tuesday, May 20, 2008 8:51 AM
To: Ene Stelian-Bogdan; Rob Mensching; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Integrate WiX in our process
I'd like to address
I'd like to address a couple things about InstallShield.In IS2009
(currently Beta) there is improved support for dynamic linking and
upgrading/patching support. Things like table primary key identifiers and
component guids should be much better behaved. Even then, I would really
hesitat
Hi Rob, thanks for your answer
The few shared files are in components defined manually, so it's not a
problem. When it comes to the thousand of (unshared) files, manually
defining components is not an option - there's no way to do it in code,
one must use Installshield's clunky GUI. This setup w
The "Dynamic linking" feature where Component Ids change with every build makes
it impossible to patch. In fact, I think the only option available to you
using that methodology for creating MSI packages is major upgrade. Also, I
assume you don't have any shared files in the "big zip file" beca
6 matches
Mail list logo