IIS Application Pool needs to be reset even after deploy

We have been getting some weird behaviour for our IIS applications where even though Octopus performs a directory change on the Website setting, it seems like our applications are still somehow being cached.

Until we do a manual IIS reset or application pool recycle for those certain applications, it does not seem to be pointing to the new application.

Any ideas?

Hi Dejan,

Thanks for getting in touch. Which version of Windows and IIS are you using, and is it x64 or x86?


IIS 7.5
Application pool is in 2.0 Runtime and 64 bit Version.

Hey mate, you can definitely close this one, I am confident it was just the way that the application was developed where it was storing a lot of stuff in memory and the application pool had to be reset because the there is no sliding window for the cache.