We have a need to have some sites running both .aspx and classic .asp. The new wizbang homepage and wrapper is .NET 2.0 and many of the resources behind the scenes is classic .asp.
The homepage and wrapper aspx pulls in some classic .asp resources to fully render pages. The homepage aspx and associated files are kept in a separate directory from all the classic .asp directories/pages.
We set up a separate single application pool to handle the homepages/wrappers of all the sites and kept the old application pools to handle the rest of the sites. (each site's classic area has it's own application pool as well).
We are seeing load times for each site as longer than before, though the amount of bits is about the same.
Question: Do you think there is a performance hit to a site that has separate app pools for it's .NET and classic portions?
We didn't think we could/should run the .NET and classic .asp all under the same application pool, but that may be a misguided thinking.