Hi
I'am in the process to write installers for our websites. A basic wish is that we should be able to install a new site with some default values ex. a specific apppool with initial values. That part of the process is handled ok. Our problem is when updating the site then changes made to the configuration, ex. the "Idletime" in an apppool is changed back to the value specified in the installation. Basicly we dont want this configuration to change on updates.
I have seen that wix operates with a "ConfigureIfExists " = yes/no on the WebSite entity but that demands that the WebSite has a "Component" object as parent.
As an alternative we can read all existing parameters on the website and the apppool and use these for an upgrade - but there is a lot of theese parameters.
What is the right strategy in the above case.
Regards
I'am in the process to write installers for our websites. A basic wish is that we should be able to install a new site with some default values ex. a specific apppool with initial values. That part of the process is handled ok. Our problem is when updating the site then changes made to the configuration, ex. the "Idletime" in an apppool is changed back to the value specified in the installation. Basicly we dont want this configuration to change on updates.
I have seen that wix operates with a "ConfigureIfExists " = yes/no on the WebSite entity but that demands that the WebSite has a "Component" object as parent.
As an alternative we can read all existing parameters on the website and the apppool and use these for an upgrade - but there is a lot of theese parameters.
What is the right strategy in the above case.
Regards