iisreset will stop et démarrez le World Wide Web Publishing Service. This, of course, applies to tous of votre application pools. Je suis sure you noticed a process being created for chaque application pool. This process will handle requests for tous websites associated avec it. When you recycle an application pool, IIS will créez un nouveau process (keeping le old one) to serve requests. Then it tries to move tous requests on le nouveau process. After a timeout le old process will be killed automatically. You usually recycle votre application pool to get rid of leaked memory (you might have a problem in votre application si this needs to be a regular operation, even bien que it is recommended to have a scheduled recycle). As for restarting a website, it juste stops et restarts serving requests for that particular website. It will continue to serve autre websites on le même app pool avec no interruptions.
If you have a session oriented application, tous of le ci-dessus will cause loss of session objects.
Refreshing a website has no effect on le service/process/website et is merely a UI command to refresh le treeview (maybe you added a directory you ne see in le management console).
