Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

What is the difference between the IIS7 application pool types

Tags:

.net

iis-7

In IIS7 you have the option the choose different application pool type. I have 4 types to choose from

  • Default Application pool
  • Classic .Net Application pool
  • ASP.NET v4.0
  • ASP.NET v4.0 Classic

What are the differences between these, and when to choose what?

like image 881
Ivo Avatar asked Jun 03 '10 11:06

Ivo


People also ask

What are the various application pool in IIS?

Application pools can contain one or more worker processes. Each worker process represents work being done for a Web site, Web application, or Web service. You can create a Web garden by enabling multiple worker processes to run in a single application pool. In IIS 7 and later, each application pool uses one of two .

What is the difference between application pool identity and network service?

Application Pool Identity Accounts Worker processes in IIS 6.0 and in IIS 7 run as Network Service by default. Network Service is a built-in Windows identity. It doesn't require a password and has only user privileges; that is, it is relatively low-privileged.

What does application pool mean?

An application pool serves as a container for your applications in IIS. It's a collection of one or more URLs that can be served by a worker process, and it provides isolation: applications that run on one application pool are in no way affected by other applications that run on different application pools.

What is the default application pool in IIS?

By default, IIS adds application pools that run integrated managed pipeline mode and use . NET Framework version 2.0 for managed code execution. Otherwise, you can specify the . NET Framework version and managed code request-processing mode.


1 Answers

Classic mode models the IIS 6.0 model in which ASP.NET is an ISAPI add-on to IIS. This mode is available for backward compatibility but lacks many of the features in the new Integrated mode. In Classic mode, IIS has its own pipeline that can only be extended by creating an ISAPI extension, which has a well-deserved reputation for being difficult to develop. ASP.Net is run as an ISAPI extension that is just one part of the IIS pipeline.

Integrated mode makes ASP.Net an integral part of IIS. Now the IIS server functionality is split into more than 40 modules that break the IIS and ASP.Net functionality into pieces. Modules such as StaticFileModule, BasicAuthenticationModule, FormsAuthentication, Session, Profile and RoleManager are part of the IIS pipeline. FormsAuthentication, Session, Profile and RoleManager were previously part of ASP.Net and didn't have anything to do with IIS.

like image 188
Neil Knight Avatar answered Oct 23 '22 04:10

Neil Knight