>> "only installs if the existing assembly is older then the one being
installed."

Do you mean the files are older based on date/time or file version
number, if it is file version then this is what WiX (or more correctly
Windows Installer) does.

>> "How do I make sure I don't replace new versions of assemblies which
we don't produce and don't control."

Again, this is default behaviour if the files have different file
versions.

Another option is to investigate whether you really need to install
these files to System32, I have tried to move a lot of System32 files to
the local application folder as this makes it much easier to control and
avoid DLL hell (avoid the GAC too as that is just a different
incarnation of DLL hell!).

Neil


-----Original Message-----
From: Daniel Hughes [mailto:daniel.hug...@tait.co.nz] 
Sent: 12 January 2010 01:06
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Windows System Folder

We are moving one of products from a old Install shield installer to a 
WiX installer.

The old Installer installs a bunch of assemblies to the System32 folder.

These assemblies are not produced by us but a required dependencies of 
our software. Install Shield has a replace if older type option so it 
checks the assemblies version and only installs if the existing assembly

is older then the one being installed.

When we moved to WiX there was no such option. Each assembly gets a 
component GUID and install shield just goes along and replaces any 
existing assemblies even if they are newer. This is causing problems as 
some of our customers are running software which relies on functionary 
only available in newer versions.

I have heard that a way to get the correct component GUID so windows 
installer doesn't do bad things is to find official Merge Modules. These

have proved to be hard to find and if the assembles have been copied or 
installed to Windows32 by some other method it will not work.

How do I make sure I don't replace new versions of assemblies which we 
don't produce and don't control.

Cheers,
Daniel

=======================================================================
This email, including any attachments, is only for the intended
addressee.  It is subject to copyright, is confidential and may be
the subject of legal or other privilege, none of which is waived or
lost by reason of this transmission.
If the receiver is not the intended addressee, please accept our
apologies, notify us by return, delete all copies and perform no
other act on the email.
Unfortunately, we cannot warrant that the email has not been
 altered or corrupted during transmission.
=======================================================================


------------------------------------------------------------------------
------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and
easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to