|
5
1
|
I am running 10 web sites on that IIS installation. Why is the FogBugz stopping the entire www server instead of that the FBZ app pool? The upgrade went smoothly, but that was a drastic step, it should be optional or better yet stop the app pool; and a warning. thanks, Mike |
|||
|
|
|
2
|
I'm going to a file a case for the engineers to review this process. I believe stopping the entire web server was the only option in older versions of IIS since since application pools didn't exist. Maybe we can detect the version and only restart the app pool when possible. There might, however, be other reasons why a full restart is required. I'll post the response from engineering here. |
||
|
|
|
1
|
I add my vote to this feature as well. We have many websites and it doesn't make any sense to restart the whole IIS. Another idea that can be quickly implemented is just to add an option to the setup that will not restart IIS. The user will be responsible for restarting the correct application pool. |
|||
|
|
1
|
Any updates on this issue? this is causing a serious problem for us. |
||
|
|
|
0
|
Any update on this, Rob? This is a pretty big issue with our installation as well. |
||
|
|
|
0
|
This is also an issue for us since we cannot restart IIS and affect other production websites to install an upgrade. |
||
|
|
