Hi Martin,
well...that's silly...if I'm ending the debug session...it's good-bye app
time...but I guess not...:/
A/w...in ref to your session pt...I'll tell u why i didn't use session...and
p/ correct me
1-session adds overhead to each webservice call
2-what's wrong w/ using global.asax?
Regards,
Mekim
> Hi mekim,
>
> App_end is never called because the debugger gets detached from the aspnet_wp.exe process when you stop debugging. When detaching, it does not end the execution of the process. The process will end after some timeout elapse. You can add trace statements to see when this happen.
> IMHO it is better to avoid adding code to global.asax file in order to manage state. Why do not you use Session, of better yet – Cache class which can store your session state?
>
> Martin
Martin Kulov - 10 Nov 2004 09:15 GMT
Hi mekim,
>> 1-session adds overhead to each webservice call
The problem with session was that is could not scale well. However in current ASP.NET version there are ways to store session state in database. It won't add any other overhead more than your class adds in global.asax
>> 2-what's wrong w/ using global.asax?
Nothing. I consider it bad practice since the code is placed in a location that does not belong to any page. Since web request are considered stateless and every page is alone for itself I prefer writing code in into each page source file. I makes finding the problems easier. From the ages of ASP 3.0 modifing the global.asa file causes the web server to restart the application and may be I am used not to touch global.asa? files also.
Regards,
Martin Kulov
www.codeattest.com