G
Guest
Hello,
I have a simple redirect on a login page:
Login_Click()
{
// ... do the login verification
try {
Response.Redirect("index.aspx");
}
catch(Exception ex) {
// Get ThreadAbortException here!
}
}
When I catch the ThreadAbortException, the redirect fails to work, and I am
left back on the login page. Subsequent attempts also result in
ThreadAbortException.
I am wondering if this would happen when the aspnet_wp process recycles the
application instance? Is there anything that can be done to recover from the
ThreadAbortException being raised?? Maybe the Server.Transfer() would be
more reliable in ASP.NET??
Thanks
-- Jake
I have a simple redirect on a login page:
Login_Click()
{
// ... do the login verification
try {
Response.Redirect("index.aspx");
}
catch(Exception ex) {
// Get ThreadAbortException here!
}
}
When I catch the ThreadAbortException, the redirect fails to work, and I am
left back on the login page. Subsequent attempts also result in
ThreadAbortException.
I am wondering if this would happen when the aspnet_wp process recycles the
application instance? Is there anything that can be done to recover from the
ThreadAbortException being raised?? Maybe the Server.Transfer() would be
more reliable in ASP.NET??
Thanks
-- Jake