Avoiding IIS Reset with mulitiple sites on the server

I have been working on the hosted server of late and have found that no matter how careful I am, I usually need to do at least on reset to get a new theme or setting to go into effect. What I absolutely need is a way to restart the website I'm working on and not the whole IIS. Usually (after hours or what not), I bite the bullet and reset the whole service.

Yet recently I've been simply restarting the associated application pool with great success. I mean, IISReset is needed sometimes to release files/services holds. For instance, when changing themes in Passageways, the Passageways.config file will be blocked (by w3wp) as soon as a change has been saved and won't go into effect, sometimes for hours.

The biggest problem with IISReset (or shutting the IIS down, compiling, restarting it) is that the entire application will be shut down and restarted. Let’s not even look at the time involved, sometimes that can be enough to make me cringe in and of itself.

The workaround for this is to recycle the application pool for the IIS-website instead of restarting the entire IIS. The easiest way of doing this is to right-click on the application pool and the choose "recycle". The best part? It happens so fast that I don't even notice any service interruption for that single site (let alone the whole of IIS).