Recently migrated the original system to iis7.5, and found that aspnetupload can only run on"ProgramIn the "classic" mode of the program pool, after the "integration" mode is adopted, aspnetupload. getuploadfile is always null. Although it is changed to a classic, it does not affect the system operation, but this mode cannot take advantage of iis7. It is equivalent to running in IIS6 compatibility mode. I don't know if the author will improve it.
The following is an explanation of the application pool "integration" and "classic" patterns on mdsn: (http://technet.microsoft.com/zh-cn/library/cc753449 (ws.10). aspx)
An application pool is a set of URLs that are provided by one or more worker processes. The application pool sets a boundary for the applications they contain, which means that no application running outside the given application pool will affect the applications in the application pool.
The application pool has the following advantages:
- Improved server and application performance. For applications that occupy a large amount of resources, you can allocate them to their own application pools to avoid affecting the performance of other applications.
- Improved application availability. If an application in an application pool fails, applications in other application pools will not be affected.
- Improved security. By isolating applications, you can reduce the chance that one application can access other application resources.
In IIS 7, the application pool has two running modes: integration mode and classic mode. The application pool mode affects server processing hosting.CodeRequest Method. If a hosted application runs in an integrated application pool, the server uses the IIS and ASP. NET integrated request processing pipelines to process requests. However, if the hosted application runs in a classic-mode application pool, the server will continue to host code requests through the aspnet_isapi.dll route, the method for processing requests is the same as that for applications running in IIS 6.0.
Most managed applications should be able to run successfully in an integrated application pool. To achieve version compatibility, they sometimes need to run in Classic mode. You should first test the applications running in integration mode to determine whether the Classic mode is required.