>> I have a situation where I need to run the same installer more than once on >> a web server. The situation is that I want to be able to install to a given >> web site once for each customer we have on the same web server. As I get >> more customers for a given product, I want to be able to re-run the original >> installer and choose a new web site to deploy to. AFAIK, I can't re-run a >> given msi. I am, however. trying to come up with a reasonable solution. >> >> The only work around I have come up with so far is to recreate the installer >> for each customer with a different Product Id. This is working Ok, but, >> now, as expected, I get multiple entries in the Add/Remove Programs list. >> In addition, this seems like a lot of maintenance to me. > > You'll need to change more than just Product ID, I believe, to correctly > follow component rules. The MSDN docs describe these rules. > > I would look into using transforms to accomplish this. > > Unfortunately, multiple installs of the same product on the same machine is > somewhat of a maintenance headache. > > ------------------------------------------------------------------------------ > Two more questions: > 1) I have looked at the component rules, and do not think I have any > problems. I am guessing there is a better place to ask about installing the > same product more than once on the same box. Any suggestions on where to go > to discuss msi issues? > > 2) When you say transforms, are you referring to XML transformations & XSLT?
This mailing list post has just about everything you need I think: http://xrl.us/beo35a See this description of component rules from that page: "MSI does not uninstall non-file-data for components that are used by multiple product codes until the final client product is uninstalled; MSI assumes that non-file data is shared. This is, of course, bunk, but that's the way it works. If your component GUID is shared by multiple product installs, then all but the last uninstall will get an Action: FileAbsent for the shared components, thus not uninstalling things other than files." I'm assuming that you're using WiX to create the new web sites you mention. Those sites will have component GUIDs that MSI will assume are shared. If you're *only* installing files then sharing component GUIDs should be OK. ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
