Application pool (application domain)

When you deploy a website on IIS, you have an option about the application pool, which was previously understandable.

The following is a detailed explanation of the application pool:

The application domain is a boundary forced by CLR to ensure that an application does not affect other applications (or does not see data in memory ). Applications directly generate the following features.

1. All web pages and web services in a web application share the same memory resources, such as global application data, session data for each user, and cache data. This information cannot be directly accessed by other or ASP applications.

2. All web pages and web services in a web application share the same core configuration settings. However, you can customize some configuration settings for each subdirectory of the same virtual directory. For example, no matter how many subdirectories a web application has, you can develop a verification mechanism. However, you can set different verification rules for each directory to allow users to access different pages.

3. All Web applications will trigger global application events at different stages (when the application domain is created or destroyed for the first time ). You can use the code in the global. asax file in the application virtual directory to append the time handler for these global application events.

4. webpage (. aspx file ). This is the basis of the Asp.net application.

5. Web Service (. asmx file ). They allow you to share useful functions with applications on other computers and platforms.

6. Hide the file with code. Based on the code model used, you can also have a separate source code file. If C # encoding is used. They have. CS extensions.

7. configuration file (Web. config ). This file contains application-level settings, which configure all projects from security to debugging and status management.

Global. asax. This file contains the event handlers that respond to global application events (for example, the events when the application is started for the first time ).

8. Other components. These are compiled assemblies, including independent components with useful functions developed by yourself or by a third party. By using components, you can separate the business and data access logic, and create custom controls.