Hello everyone,

I am currently developing our company's first install with WiX, everything
before was homegrown installers or InstallShield. My WiX-based install
distributes files that may also come with other installers for our product
and it is very, very important that the WiX-based install will not install
into directories (that the user chose) which contain files that came with
other installers. So the best would be to just not let the user choose a
directory where files reside that came from our other installs. After
experimenting a bit I finally decided to bite the bullet and write a custom
action DLL (can be found here:
http://mcblogs.craalse.de/skufiles/2007/custact.zip) that scans the File
table and tests for the existence of all files in this table's FileName
column in the INSTALLDIR the user provided. If such a file can be found, a
messagebox is shown and the install aborted, because this is an attempt to
install into a directory where other installer of our products have
previously installed into.

While this all works I wonder if there is an easier way to achieve the same
result, maybe without a custom action DLL? Any clues anyone?

-- 
Stefan

-- 
View this message in context: 
http://www.nabble.com/Prevent-overwrite-of-existing-files-tf3167486.html#a8786686
Sent from the wix-users mailing list archive at Nabble.com.


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to