Its so surprising to get error while exporting the asp.net web page into excel when we write the code in try catch block. Actually its not the problem of the try catch blcok. ERROR:Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack

Take a look at the following code.

try
        {
            errorLogging.Log("abcd", System.Diagnostics.TraceEventType.Error, "NEw title");
            Response.Clear();
            Response.AddHeader("content-disposition", string.Format("attachment;filename={0}.xls", fileName));
            Response.Charset = "";
            Response.ContentType = "application/vnd.xls";

            StringWriter stringWrite = new StringWriter();
            HtmlTextWriter htmlWrite = new HtmlTextWriter(stringWrite);
            grdGridView.RenderControl(htmlWrite);
            Response.Write(stringWrite.ToString());
            Response.End();

        }
catch (Exception exception)
        {
            errorLogging.ExceptionHandlingLog(exception);
            throw exception;
        }

The above code looks so formal but an error arises…

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

The above error arises bcoz of the Response.End( ); in the above code which aborts the current thread since the request will be ended. To solve the error, you can either remove the try-catch block or if you need to catch the exceptions then you need to catch for ThreadAbortException besides catching for other exceptions. This ThreadAbortException will be caught for nothing.

This entry was posted on Tuesday, June 2nd, 2009 at 9:11 pm and is filed under ASP.Net, Programming, Web. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.