Thanks for the idea. I don't think that will work because:
a) Version 1 of the install has already shipped, so my upgrade still won't have a registry key to look for
b) Even if there was a registry key, it wouldn't guarantee that the install wouldn't be changing some settings that the user has cu
Title: Re: Web Application Pool
What about saving a registry key for each Web Component where the AppPool name is stored. On an upgrade a registry search for the key can be done and used to put it in the correct pool. Dunno if this viable, just an idea.
Morten
--
he functionality / performance a "neighbor".Just my .02.David AdamsMSN MessengerID: [EMAIL PROTECTED]> From: "Tina Basinger" <[EMAIL PROTECTED]>> To: wix-users@lists.sourceforge.net> Subject: [WiX-users] Web Application Pool> Date: Fri, 20 Oct 2006 15:21:03 -0500> MIM
/
performance a "neighbor".
Just my .02.
David Adams
MSN MessengerID: [EMAIL PROTECTED]
>From: "Tina Basinger" <[EMAIL PROTECTED]>
>To: wix-users@lists.sourceforge.net
>Subject: [WiX-users] Web Application Pool
>Date: Fri, 20 Oct 2006 15:21:03 -050
Is there any way to keep the Wix custom actions from createing or configure a web application pool (WebAppPool element) if it already exists?
Thanks!-Tina
--
-
Using Tomcat but need to do more? Need to support web servic
5 matches
Mail list logo