Why the DLL always be handled after I set the ASPCompat to true?

[Tang Heng]

I am checking a bug on a web application. ( ASP.NET 2.0 application)
And the web application will call a COM dll to write log and do other things.

After runing the application and show a page, the Log dll always be handled.

I checked the page and set the breakpoint on the OnPreInit method of the page.
When breaked, the Log dll has been handled.

Then I find the ASPCompat attribute value in the page node is true. If I
modify the value to false, the Log dll will not be handled.

So I want to know, when set the ASPCompat to true, why the dll will be
handled and how to release it.

Thank you!

 

[Bob Barrows]

I am checking a bug on a web application. ( ASP.NET 2.0 application)

***canned wrong-newsgroup reply************************
There was no way for you to know it (except maybe by browsing through some
of the previous questions in this newsgroup before posting yours - always a
recommended practice) , but this is a classic (COM-based) asp newsgroup.
ASP.Net bears very little resemblance to classic ASP so, while you may be
lucky enough to find a dotnet-knowledgeable person here who can answer your
question, you can eliminate the luck factor by posting your question to a
group where those dotnet-knowledgeable people hang out. I suggest
microsoft.public.dotnet.framework.aspnet or the forums at www.asp.net.
******************************************************************