I am tasked with writing an installer to deploy some (.NET) web services on IIS. Typically the deployment will involve some/all of the following: During install selecting: . The App pool (test that the AppPool the user chooses is compatible with the service/application being installed) . The website to use - IIS can host more than one website . The virtual application and the URL that the service will be accessible by. . Various changes to XML config files that are installed o Connection strings for the service to connect to a database (we allow multiple connection strings) o Some general application settings (output directory for results of the service, location of some other installed products on the machine, etc.) . Enabling the distributed transaction coordinator The web service is a pretty complicated and this list of requirements will undoubtedly grow. I can generate a web deployment package which automates some of this stuff (and, till now, have been doing the rest manually, e.g., in IIS). My question is related to creating a Wix installer for this stuff - should I start from scratch and implement all the steps natively in Wix, or should I create the web deployment package and install it by implementing a custom action that calls the web deploy application, then do any additional stuff in Wix. If anyone can point me to information about how best to accomplish this, it will be much appreciated. Thanks sanjay ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
