The ASP Classic application will run in the application pool to which it is assigned.
An ASP.NET application also runs in its designated application, therefore, it is possible that one or more ASP.NET applications and one or more ASP applications will run in the same pool and, therefore, share the process (s).
In IIS6, there is a small connection between the two (ASP and ASP.NET applications), they simply perform their task side by side. They use the same virtual memory space, so if someone is afraid of the other, it affects. In addition, if one of the processes terminates, all other applications in the pool (ASP and / or ASP.NET) will be affected. They also use a common ISAPI filter stack, which runs on a per-process basis.
In IIS7 with an integrated pipeline, things are also becoming more integrated. ASP classic relies on a .NET-based pipeline to deliver requests for processing.
AnthonyWJones
source share