Скачать или смотреть Understanding the IISReset: What Happens When You Reset Your IIS?

Learn what `IISReset` does in your web server environment and how it compares to other operations like recycling app pools and managing web applications.
---
This video is based on the question https://stackoverflow.com/q/23566/ asked by the user 'Guy' ( https://stackoverflow.com/u/1463/ ) and on the answer https://stackoverflow.com/a/23571/ provided by the user 'hova' ( https://stackoverflow.com/u/2170/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, comments, revision history etc. For example, the original title of the Question was: What does 'IISReset' do?

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 2.5' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Understanding the IISReset: What Happens When You Reset Your IIS?

When you're working with Internet Information Services (IIS), it's crucial to understand the impact of different server management commands. One common command is IISReset, but what does it really do, and how does it compare to other actions like recycling an app pool or starting and stopping a web application? This guide will delve into these concepts, helping you grasp the differences and implications of each action on your web server's behavior.

What is IISReset?

IISReset is a command that stops and restarts the entire IIS web server. This means:

Total Shutdown: All applications under IIS will be stopped, including ASP.NET applications as well as any other non-ASP.NET applications hosted on the server.

Full Restart: Once the server restarts, it reloads all the websites configured within IIS.

When to Use IISReset

You might consider using IISReset in circumstances such as:

Major updates or configuration changes that require a full restart of IIS.

Troubleshooting server-wide issues where a simple application-level restart isn’t sufficient.

Recycling App Pools: A More Granular Approach

In contrast to IISReset, recycling an application pool affects only the web applications running within that pool. Here’s more about app pool recycling:

Targeted Recycling: Only the specified app pool will be recycled, meaning other apps and pools remain functional during this process.

Minimal Downtime: This approach minimizes impact on the overall server, as other sites hosted outside the affected pool continue to run.

Advantages of Recycling App Pools

Less Disruption: Users may not notice the changes as other applications keep running.

Quick Troubleshooting: If an application is misbehaving, recycling its pool can resolve the issue without affecting the entire server.

Stopping and Starting an ASP.NET Web Application

Stopping and starting an individual ASP.NET website is another action that differs from both IISReset and recycling app pools. Here's how it works:

Application-Specific: Only the website you target is affected. Other applications, whether in the same pool or not, remain online and accessible.

When to Use: This is particularly useful when you make changes to the site, such as updating a DLL or modifying the web.config file.

Impact of Changes in ASP.NET Applications

When you edit or replace the web.config file or other DLLs in your ASP.NET application, here's what happens:

Automatic Recycling: IIS monitors the /bin directory of your application. If changes occur, such as new DLLs, IIS will automatically recycle the app and reload the new components.

Config Changes: Similar monitoring applies to the web.config and machine.config files, triggering recycling for all affected applications.

Key Differences Recap

To clarify the distinctions among the various actions:

IISReset: Stops and restarts the entire server; affects all hosted applications.

App Pool Recycling: Affects only specified pools; allows other applications to continue running.

Restarting an ASP.NET Web Application: Only targets the individual site, ensuring other sites remain unaffected.

Conclusion

Understanding the differences between IISReset, recycling app pools, and managing website states is pivotal for efficient server management. Each option serves a unique purpose, catering to specific situations in web development and system administration. By grasping these concepts, you can ensure smoother operations and better performance for your hosted applications.

Whether you’re troubleshooting issues, implementing updates, or maintaining your server's health, choosing the right command can make all the difference.