You could try adding a custom action that adds (temporary) rows to the
appropriate tables for the built-in actions that setup webservices. Bob
called them "semi-custom actions".
(http://www.joyofsetup.com/2007/07/01/semi-custom-actions/)

Just make sure that you save and/or compute somehow the information you need
to recreate those rows for repairs, upgrades, and removals, since you may
not have the same command-line...

-----Original Message-----
From: Adam Burton [mailto:adz...@googlemail.com] 
Sent: Wednesday, May 26, 2010 10:38 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Advice

Hi,
I have a project that installs a web service with some XML files. Currently
IIS 
is not configured by WiX, so for the most part it just dumps the files in a 
specified location and fixes some path details in its web.config. One of the

requirements that has now surfaced is for the web service to exist multiple 
times with different configurations, more than likely on the same server. As

such I would like to add the option of installing the web service multiple 
times, but I do not have a specified number of times. The directory
structure 
looks something like below.

C:\MyService
      \WebService
          \bin
          service.asmx
          web.config
      \XmlFiles
            files.xml
            ....

Currently we install it then copy paste the webservice directory however
many 
times required (the XmlFiles directory does not need to be unique per 
service).

The only options I see are to have a custom action copy the directory based
on 
properties that could be passed to the installer.
The another method is a multiple instance installer, which from what I
gather 
requires transformations, but I could only see how to do this with knowing 
upfront how many instances you need.
Alternatively on the off chance someone knows, the only thing that changes 
between these copies of the web service directory is the contents of the 
web.config, so is it possible to point multiple IIS vdirs/websites at a
single 
directory and get each one to use a different web.config?

Anyone have better ideas or better reading material on multiple instance 
installers (also bare in mind that in the future I would like to persuade my

boss to let the installer configure some of the IIS bits, but not a priority
at 
the moment)?

Thanks in advanced,
Adam

----------------------------------------------------------------------------
--

_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


------------------------------------------------------------------------------

_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to