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
--
I think we have one application pool per web site as well. However, I am working on an upgrade scenario, and do not want to re-configure the application pool if it exists because the user may have updated settings on it since the original install. The same applies for the web site we create, but
Tina:
I am not sure the answer to your question, but we create application pools
for each of our web sites in IIS. Because we have a multiple web site /
shared server resource environment, having dedicated application pools
prevent problems in one web site from impacting the functionality /
p
4 matches
Mail list logo
