> -----Original Message----- > From: Nick Ball [mailto:nick.b...@grantadesign.com] > > The problem I had is that management were very reluctant for me to spend > the time getting up to speed with WiX. Setup is just copying a few files > right? > How hard can it be?!? In reality we have many different configurations of the > product, all of which must product a nice simple setup.msi. >
Even copying files correctly to support upgrade is not a very simple process. I assume your custom solution would keep a manifest of the files it installed becoming the previousVersionSet. Then there's the files the upgrade wants to install becoming the nextVersionSet. And we all know that Ops guys can and will change files on disk as they desire so there's a currentSet. Files you installed with previousVersionSet that need to be overwritten by files in nextVersionSet are generally easy to deal with. What if there is a file in currentSet that also exists in nextVersionSet but doesn't exist in previousVersionSet? In other words, the upgrade installer will overwrite a file that was "installed" by somebody else... We're getting into some very dangerous waters here and all we are doing is copying a few files... It turns out this can be very hard indeed! Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com Please consider the environment before printing this e-mail ------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
