We have a product which include a number of features. One of these features installs a virtual website under the Default Web Site. Each feature is defined within its own fragment
Initially the website element refering to the Default Web Site was added under the Product element. We had an issue in that if you chose to install only the client app feature (which does not install the website) to a machine does not have IIS the installation fails trying to configure IIS due to the fact that the WebSite element is a child of the Product. I haved moving the WebSite element into a Component. As we are installing to a virtual directory under the Default Web Site. I had to make the component permenant to ensure it isn't removed on uninstall. I assume this component will need to be embedded in a Directory element which refers to the local wwwroot folder. I haven't been able to find any examples of this scenario so any guidance would be appreciated on the best practises. Stuart ----------------------------------------------- This mail sent through http://webmail.zoom.co.uk ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
