Thursday, 10 March 2011

Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack

I got this error when using Response.Redirect in a Try-Catch. I'd never seen it before, but it is resolved by specifying 'false' after the URL like below. This tells the execution of the current page not to terminate:

Response.Redirect("whatever.aspx",false);

No comments:

Post a comment

Comments are moderated, so you'll have to wait a little bit before they appear!