From d400539a43c1b9811b96b934b65400216e3f73f2 Mon Sep 17 00:00:00 2001 From: Fenton Hutson <112075131+FentonPlusPlus@users.noreply.github.com> Date: Wed, 1 Oct 2025 08:40:52 +0100 Subject: [PATCH] Update getting-started-with-the-iis-manager-in-iis-7-and-iis-8.md Grammar error --- .../getting-started-with-the-iis-manager-in-iis-7-and-iis-8.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/iis/get-started/getting-started-with-iis/getting-started-with-the-iis-manager-in-iis-7-and-iis-8.md b/iis/get-started/getting-started-with-iis/getting-started-with-the-iis-manager-in-iis-7-and-iis-8.md index 9525e919b..c7cf930ac 100644 --- a/iis/get-started/getting-started-with-iis/getting-started-with-the-iis-manager-in-iis-7-and-iis-8.md +++ b/iis/get-started/getting-started-with-iis/getting-started-with-the-iis-manager-in-iis-7-and-iis-8.md @@ -27,7 +27,7 @@ IIS 7.0 and later have a new user interface from previous versions of IIS: the I - **IIS and ASP.NET work together**: IIS 6.0 users right-click on a web site, select "All Properties", and get a dialog with a number of tabs for different settings. With IIS 7.0 and above, IIS Manager needed to show configuration for new features like Output Caching, [Failed Request Tracing](../../troubleshoot/using-failed-request-tracing/troubleshooting-failed-requests-using-tracing-in-iis.md), and [Request Filtering](../../manage/configuring-security/use-request-filtering.md), as well as configuration for ASP.NET and relevant portions of the .NET Framework. The new functionality would have required many more of new tabs, an unacceptable option. - **Delegated Administration**: Moving our configuration from the metabase to the .NET configuration system means that users can, if permitted, set IIS configuration in web.config files. For example, configuration for an application ```http://www.contoso.com/sales``` can be written to the root config file applicationHost.config, to the site ```http://www.contoso.com/``` web.config file, or directly to the application's web.config file. The new IIS Manager has to: 1) allow an administrator to control the configuration permitted in web.config files, 2) show the administrator/user where configuration is being written. The older IIS Manager was not up to these challenges. -- **Engineering Reasons**: Software has a shelf life. Time brings new technologies, new requirements, new conventions, and there comes a point where updating existing software becomes more labour intensive and costly that rebuilding the software. IIS Manager was approaching the end of its shelf life. +- **Engineering Reasons**: Software has a shelf life. Time brings new technologies, new requirements, new conventions, and there comes a point where updating existing software becomes more labour intensive and costly than rebuilding the software. IIS Manager was approaching the end of its shelf life. **Anything else to know?** Once we decided to rewrite IIS Manager, we took the opportunity to improve in a number of key ways: