When you finish your IIS 10.0 installation, you will get the default application pools and default web site. The application pool works on worker process or a set of worker processes for one or more websites.

Application pools are used to separate sets of IIS worker process that share the same configuration and application-level boundaries as your web applications. This is a really great feature of IIS and helps us run our web applications.

The benefit of application pools is that if you have an issue with one of the application pools, it will only effect the associated application pool.

Application pools enable us to isolate our web application for better security, reliability, and availability.

Two types of application pipelines are available. We can select integrated mode (supports IIS 7.5 or later versions) or classic mode (IIS 6.0).

In this recipe, we will understand application pools. We can simply say that the application pool is the heart of IIS 10.0. Application pools are logical groupings of web applications that will execute in a common process, thereby allowing greater granularity over which programs are clustered together in a single process. For example, if you require every web application to execute in a separate process, you simply go and create an application pool for each application of different framework versions.

Let's say that we have more than one version of a website, one that supports framework 2.0 and another one supporting framework 4.0 or some different application such as PHP or WordPress. All these website process are managed through application pools.

In this recipe, we are going to install framework 3.5 on Windows Server 2016. By default, IIS 10.0 has framework version 4.0. We will install the lower version of the framework, which supports web applications with .NET framework versions 2.0 through 3.5.

For example, if you have a web application you created a few years back and it was developed in the v2.0 .NET framework, you can use this recipe in order to make it run on IIS 10.0. Let's begin.

To step through this recipe, you need to install framework v3.5, which is based on the v2.0 framework. You will need a Windows Server 2016 instance. You should have the Server 2016 OS media for the framework 3.5 files or an...

In this recipe, we are going to create an application pool that supports .NET versions 2.0 to 3.5. We already have the default application pool available for 4.0. This recipe will guide you through creating the different application pools you require.

In this recipe, we need IIS 10.0 and .NET framework 3.5. You should have administrative privileges.

1. Open Server Manager on Windows Server 2016. Click on the Tools menu and open IIS Manager.

2. Expand the IIS server (WIN2016IIS). You'll get...

In this recipe, we will have an overview of application pool properties. We will check out the default configurations under Basic Settings, Recycling, and Advanced Settings. This is very helpful for a developer or system administrator as one can configure different properties of different application pools based on application requirements.

For this recipe, we need IIS 10.0 and any version of the .NET framework installed on IIS 10.0. You must have administrative privileges.

1. Open Server Manager...

In this recipe, we are going to host a .NET default v4.0-supported web page. We will check out the default website properties. We will upload the web page to the default wwwroot directory.

We need a v4.0 application to be installed on IIS 10.0 Server, and our v4.0 .NET web page should be ready. We'll need to install some IIS components not installed already in IIS 10.0. For this, you must have administrative privileges.

First, we have to install some .NET supported components.

1. Open Server Manager on Windows Server...

In this recipe, we are going to host a .NET v2.0-supported web page. We will change the property of the Default Web Site. We will upload the web page to the default wwwroot directory.

We already have the v2.0 and v3.5 framework versions installed on IIS 10.0 Server. The v4.0 .NET web page we created should be ready. You must have administrative privileges.

1. Open IIS Manager and click on Default Web Site.
2. In the Actions pane, click on Basic Settings... and then click on the Select... button, highlighted...

In this recipe, we are going to test the v3.5 application pool we created. Also, we will test the default v4.0 application pool.

We are going to test the v4.0 and v3.5 frameworks. We have created both the files and already uploaded them to wwwroot folder.

In this recipe, we need the already configured v4.0 and v3.5 frameworks. For the web pages, we've already created the v4.0 and v3.5 framework application files. One by one, we will test the localhost URL and see the result. We will also test across versions of frameworks and web application files.