>>If your log entry for "Application Start" is coming from "Application_Start" in global.asax then I think there is something seriously strange. That should only fire on start-up and (generally speaking) only again if the application has to re-start (as in the re-cycling process)
>>It certainly shouldn't end after each page hit....
>
>Application_Start() fires when a new DLL is effective or on recycle. In this case, a new DLL was effective.

OK. That wasn't clear. To be sure: you're saying a DLL was replaced immediately prior to each occurrence of 'Application End' ?

>
>>The TestForm page has the one second Sleep() in Page_Load() (this happens *before* the Page_Load log entry). The first three hits are more than one second apart so no additional instances of HttpApplication are required. The next three are less than a second apart. The first uses the existing instance the next two create additional instances because the first page has not been complete.
>>BTW nothing has changed with the HttpApplication Init() method ; here's my logging code:

Public Overrides Sub Init()
>>        Logger.LogAction("Application Init")
>>        MyBase.Init()
>>    End Sub

>>Application_Start should only fire once when the website starts up (I assume it's a shared method) - I have no idea why you are getting Application_End after each page hit.
>
>I still don't understand how you are getting Application_Init() to be used. In my case, this event never gets fired in the Global.asax file.

Application_Init() does not exist and Init() is not an event - its an overridable method. Are you saying that with the above code in the global it never gets called?

Also, as per yesterday, I'm not sure that you have really narrowed this down to something that only happens when the application re-cycles. Unless you try with the long-running page and over-lapping hits and never get the problem it's not proven.

BTW the HttpApplication.Dispose() may get called at any arbitrary point - I think that's down to how the HttpApplication pool is managed.

>BTW, I also checked the KB and it was already installed on my PC. When I tried to install it again, it told me that.
Noted.