Strange Error
-
Hi, I got the following exception error when I debug my .net application in 2005. "Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack." Actually I am binding the data to gridview. I am sure that the data is there in dataset and binding to gridview. while binding, I am getting the above error. I have searched in net, I got the solutions like, run in mixed mode (managed and native). I did the same means, I enabled both managed and native code debugging options. But still I am getting the same error. Could you please tell me how can I solve this? I am using windows 2003 server with service pack 2. Thanks in Advance,
AR Reddy
-
Hi, I got the following exception error when I debug my .net application in 2005. "Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack." Actually I am binding the data to gridview. I am sure that the data is there in dataset and binding to gridview. while binding, I am getting the above error. I have searched in net, I got the solutions like, run in mixed mode (managed and native). I did the same means, I enabled both managed and native code debugging options. But still I am getting the same error. Could you please tell me how can I solve this? I am using windows 2003 server with service pack 2. Thanks in Advance,
AR Reddy
-
Hi, I got the following exception error when I debug my .net application in 2005. "Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack." Actually I am binding the data to gridview. I am sure that the data is there in dataset and binding to gridview. while binding, I am getting the above error. I have searched in net, I got the solutions like, run in mixed mode (managed and native). I did the same means, I enabled both managed and native code debugging options. But still I am getting the same error. Could you please tell me how can I solve this? I am using windows 2003 server with service pack 2. Thanks in Advance,
AR Reddy
Hi Reddy, Interesting error! On googling a bit i found that it can be because of the response.redirect method in the catch block! The response.redirect normallu throws out a thread abortion error so in the catch block it is throwing this error. Remove your response.redirect in your catch block i guess it should work fine! If you want to redirect to a specific on an exception use the web.config instead Hope this helps!
gauthee