elsewhere home of a .NET geek

  Home  |   Contact  |   Syndication    |   Login
  21 Posts | 1 Stories | 52 Comments | 35 Trackbacks

News

This blog has random information about Managed Code and Design Pattern. Every day, while i code, the thoughts come in mind are the one you would be reading here.

If you're seeking me for asking any questions, please use the contact page of this site.

Twitter












Article Categories

Archives

Post Categories

In .NET 2.0 i had a serious bug and screwed my head, for me the below code looks fine,

        try{

if (retVal == 0)
Response.Redirect("Success.aspx?evt=0");

if (retVal == -2) //Email-Id is already present
                Response.Redirect("Success.aspx?evt=1");

if (retVal == -1) //Some error occured
                Response.Redirect("Success.aspx?evt=2");

}
catch(Exception error)
{
Response.Redirect("Success.aspx?evt=2");
}
finally{}

I sware there is no bug in this code, when tried to execute this code it creates an exception

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

I was stunned by seeing once after i commented the try catch block, it worked fine. Guys, any idea about this?

posted on Saturday, February 25, 2006 3:16 PM

Feedback

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 2/25/2006 5:51 PM scottgu
Response.Redirect thows an uncatchable exception when it is used. That might be why your catch block isn't firing (or maybe it is firing -- in which case Response.Redirect is being called twice).

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 2/26/2006 4:31 AM Vadivel Kumar
You might be right. But since the catch block can catch all "Exceptions", how can Response.Redirect throw "uncatchable" exception, which looks irrevelent.

BTW, I tried to debug whether the Response.Redirect is being called twice, but it is called only one time. Once the execution comes to any "if" condition and execute Response.Redirect the exception occurs.



# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 2/26/2006 4:36 AM Vadivel Kumar
But, what the bug is meant about? I could't understand "native frame is on top of the call stack" -- ???

:)

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 2/26/2006 4:59 AM Vadivel Kumar
Hi scott,

First of all sorry to ask this question here. I tried alot to find out everywhere (even in your blogspace) but couln't found any thing appropriate.

Is there any way to give namespaces manually or making it automatically in VS 2005, as like in VS 2003. I am so bugged because, it creates the dll names with inconvinient names and also it creates n number of dll files. I just want to have one or two dll files based on like BL and DAL etc.,

I tried to use the Web deployment project and i got the error "aspnet_merge exited with code 1". I could do nothing with this error and the post in your blogpsace is also closed :(

Please consider this as a urgent case and hope you'll help me.

Thanks

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 2/26/2006 5:36 AM jeelz
Looks like yr response.redirect in the try is throwing a thread being aborted exception which causes the execution flow to go to the catch where u r doing another redirect which again causes an exception - if u comment out the redirect in the catch block and just spit out the exception in a Response.Write (maybe) what do u see?

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 2/26/2006 6:04 AM Vadivel Kumar
It worked.

But the issue is slightly different. Lets assume, that as soon as an exception is caught in the catch block i am trying to redirect to a page where i will deal with the exception. I think, this is a straight forward way.

Iam wondering why in a catch block the Response.Redirect is not working.

Is there any thing that inside a catch block, we should not redirect to another page :)



# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 3/2/2006 9:52 AM Brian
2 Things.

First, try using the second response.redirect method passing true to end the response. e.g.

Response.Redirect("Success.aspx?evt=1", true)

Second, create a class library project and add that to your solution to get a single dll ala bl dal etc.

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 3/2/2006 4:16 PM Vadivel Kumar
No, its not possible to end the response since the page has to do more things :)

So, i cant use end here.

How can you say that separate dll file can solve this problem? can you elaborate it?



# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 3/16/2006 1:02 PM Brian
If you need your page to do more things then set a flag e.g. IsRedirecting, do your cleanup code and then redirect.

If you create separate libraries for your data and business layers then they will compile to single dll files instead of the multiple ones you were seeing. (Or maybe I just don't understand what you're asking)

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 3/24/2006 7:06 AM Eric Golpe
I also get the same exception.. I am calling a simple redirect, and catching and logging the exception..

I tried Server.Transfer, preserving the form data, but no dice.. and I too have mutiple dll's referenced inthe same solution. Perhaps this is a debugger issue only?

I'm not sure why that would be..

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 3/24/2006 2:06 PM Phil
I'm getting the same problem. It's probably a .NET bug that's gonna be blagged as a feature as usual!

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 3/24/2006 2:06 PM Phil
I'm getting the same problem. It's probably a .NET bug that's gonna be blagged as a feature as usual!

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 4/4/2006 12:32 PM Kerry
I just got the same error when I moved my Server.Transfer/Response.Redirect into the try block.

Previously it was outside and it worked fine (except I don't want it to redirect unless everything is successful which is why I moved it in).

For now I'll use a bool but I'm hoping Scott might provide some insight. Very strange exception...

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 4/4/2006 5:42 PM Vadivel Kumar
I guess, it is a problem in ASP.NET itself. Do yo u guys may get same sort of problem in using try..catch blocks with any other classes (like Response/Server classes)

Please do add it up here.

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 4/12/2006 5:35 PM manuel
Well Response.Redirect always threw an aborted thread since the end of times.
Have a look at this:
http://support.microsoft.com/kb/312629/EN-US/

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 4/13/2006 4:18 AM Vadivel Kumar
As per this article states - use the try-catch block to catch the ThreadAborted exception but the problem comes while trying the catch the exception.

I dont think this is the cause for this error. May be something else.

One more thing here is that the error message is very generic and means in broad ( <i>Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack</i> )


-
Vadi

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 5/4/2006 1:16 PM Dexter McCloud
I'm not exactly sure of the intent of the error message but I got around the error by testing to see if the message contains the "Thread is being aborted" message. Here's an example:

if (ex.Message.StartsWith("Thread") == false)
{
Response.Redirect("~/Error.aspx?ErrorMsg = " + ex.Message);
}


# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 5/12/2006 3:13 AM Erus Nauction
Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. <-- this error is usually only caused if your response.redirect is in a file that is in a frame. Seems response.redirect doesn't work with frames.

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 6/2/2006 4:20 AM Chandana N. Athauda
Pls try this link : http://support.microsoft.com/kb/312629/EN-US/

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 6/9/2006 4:48 AM Mohit
response.redirect("nextpage.aspx",false);
worked for me.

reference:
http://support.microsoft.com/kb/312629/EN-US/


# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 7/18/2006 4:24 PM Garb'o
yes, if you use false in the second parameter it will work just fine

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 7/26/2006 3:35 AM JunB
Thanks, it works for me too.

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 10/24/2006 1:41 PM prd
hi.. sorry if this has been answered already, I don't have time to read all replies..

your exception is probably caused by the finally {} - as you can see in all possible paths the code will execute a Response.Redirect(), therefore the finally can never be executed.

Remove the finally {} since it does nothing anyway

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 11/16/2006 10:21 PM Justin
I too was getting this problem, I had to move the response.redirect out of the try block and it worked. Putting a true or false in the 2nd param of the redirect didn't help.

# BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 2/20/2008 4:11 AM Prabhakaran
Hi,

i used in my page Response.Redirect("Events.aspx"); within try catch block

but it is showing execption like "Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack." can any one clear that why it throw exception

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 3/10/2008 8:55 AM Amey
Response.Redirect("Events.aspx", false); will work for u.

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 4/8/2008 5:39 AM hardik
hi
i m getting error

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


when i try to execute code for file open/save as dialog box

----------------------
Response.Clear();
Response.ContentType = "application/octet-stream";// type;
Response.AddHeader("content-disposition", "attachment; filename=" + name);
Response.AddHeader("Content-Length", objFileInfo.FullName.Length.ToString());
//Response.TransmitFile(path);
Response.WriteFile(path);
Response.Flush();
Response.End();
-------------------
after this browser run for infinite time and in catch i got error msg.
"Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack."

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 5/30/2008 5:42 AM Manoj Chakale
If u get an exception when you are using
Response.Redirect("ABC.aspx")

Instead of that overload this method and use as follows
Example:

Response.Redirect("ABC.aspx",false)

I have tried it. It works fine

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 6/4/2008 1:39 AM asdfg sfgsdgsd f gsdfgdfgsdfgdfg
sadf asdf sdf dfasfaskdfs kasd fasdfuhsiadfh iasdif asdgfg asdlfsdl fasg ifsgf asid shvaisufhu uh

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 6/12/2008 3:37 AM b-styler
http://support.microsoft.com/kb/312629/EN-US/ worked fine,
thanks.

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 6/24/2008 10:40 AM Juan
Hi guys, i had the same problem, and i fixed it just taking out my code from the try - catch block, and now works perfect.

Thanks a lot!!

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 6/30/2008 8:19 AM Vikram Vyas
Yes, passing a bool "false" worked for me...!!! thx

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 7/28/2008 12:13 AM Yuvraj Nipankar
I am also facing the same problem while file exporting with in the code, I go through the forums and the solution iworked for me is just remove the Try chatch block OR put Response.End out side of the try cahtch block i will resolve the issue.

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 8/26/2008 9:03 AM suresh
I was stunned when i see the error "Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack".

But at last i resolved the issue by adding a parameter "false" after the querystring. eg: Response.Redirect("Default.aspx?id=1,false");

Happy programming

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 8/26/2008 9:15 AM Arun
Thanks Suresh for the help. Your reply helped me in solving the issue. Great Job.

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 8/26/2008 9:22 AM Suresh Thomas
Mr.Arun

I think you are a fresher in programming. That's why you are saying that it's a great job. Try to find new innovative programming techniques rather than working in the same job.

regards

I am the answer

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 8/27/2008 11:48 AM Vagner Santos
I could solve my issue when I set the endResponse parameter.

Response.Redirect(Request.Url.LocalPath, false);

Regards.

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 11/6/2008 11:41 PM Priya
If you people need to use response.redirect when line of code written in try are executed successfully then use one int variable as flag and set its value initially to zero and in catch block make it -1 and check value and then below finally block use if and do response.redirect.
This way my problem is solved.

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 11/29/2008 7:19 AM Arthur Milfait
hi,

im not using asp.net, but i may contribute some information, that help you understand the problem.

i am implementing a heavily multithreaded application and i also get this exception now:

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

in my case the cause for this exception is, that a thread calls Abort() on its own thread-object representation (like MyThread.Abort();). this call happens in a try-catch-block, but the exception is raised not there. it is raised in the method the thread was originally created with (this might be the reason why i read that an "uncatchable" exception is raised - it seems it is just raised where you dont expect it). i have a catch there too (allthough i expected a "ThreadAbortException"), so i have been able to figure out this problem

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 1/7/2009 1:25 PM Kshama
try this it solve my problem.

http://support.microsoft.com/kb/312629/EN-US/


# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 1/11/2009 1:34 PM DotNetGuts
For solution on Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack

http://dotnetguts.blogspot.com/2009/01/unable-to-evaluate-expression-because.html



# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 2/16/2009 1:45 AM eMan
i am developing an app in facebook. When user session is null , I need to redirect to facebook login page. Since the app is in Iframe, response.redirect will cause the whole facebook page to load in the IFrame. so I need to use javascript. All my facebook api calls is in a Class, so this is my code
((System.Web.UI.Page)System.Web.HttpContext.Current.Handler).ClientScript.RegisterStartupScript
(typeof(Services), System.Guid.NewGuid().ToString(), string.Format("window.parent.location.href='{0}';", strUrl), true);


My issue is that I need to end the response right after this statement. since no code should be executed when session is not there. So i added

System.Web.HttpContext.Current.Response.Close();
System.Web.HttpContext.Current.ApplicationInstance.CompleteRequest();

Its throwing my the error "Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack"

because the response has ended. WHat should i do in this case



# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 3/6/2009 8:11 AM Diego
I'm having the problem when I execute the following code:

Response.Clear();

Response.AddHeader("content-disposition", "attachment; filename=vnd.xls");

Response.Charset = "";

Response.Cache.SetCacheability(HttpCacheability.NoCache);

Response.ContentType = "application/vnd.xls";

System.IO.StringWriter stringWrite = new System.IO.StringWriter();

System.Web.UI.HtmlTextWriter htmlWrite =
new HtmlTextWriter(stringWrite);

gdvReport.RenderControl(htmlWrite);

Response.Write(stringWrite.ToString());


Response.End();

I tried every possible solution mentioned here but none of them worked. When I debug this, the error happens when the Response.End() is executed

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 8/26/2009 12:11 PM suman
This error is because u are calling response.redirect between try catch block, when response. redirect under try block is executed catch block in the call stack never executes.

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 10/20/2009 8:15 PM prashant phalle
Response.redirect("page.aspx",false);
wokred for me.

Thanks,
Prashant Phalle

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 12/14/2009 8:46 PM João Rollo de Sá
One Solution since you dont want to interrupt the normal page flux of the response.
When you get the content to be generated you send that content to a Session Variable...
for ex. in the page export event handler :

Session.Add("MyReport",reportDataString);

Then you use an http Handler to generate content :
instead of response end you do:

Response.Redirect("~/panels/reports/exportExcel.ashx" , false);

The HTTPHANLDER "exportExcel.ashx" has to either implement the interface "IReadOnlySessionState" (for session readonly access) or in case you want to clean the session that has the report generated chunks(html, pdf etc), you implement the interface "IRequiresSessionState"
to write/read access to the session object.
I know this is not the best solution but this was the only one that avoided that exception from being Throwned..

Cheers,

João de Sá






# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 1/6/2010 3:32 PM pervek Kabir
I solve this problem
like that way Response.redirect("URL",false);

But when i publish and upload in my webserver then that is not working, page is refrishing just.

how can i solve this. andy successfully execute vai IIS service.

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 1/7/2010 2:31 AM Oliver Kiss
Response.Redirect(URL, false); works just fine!

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 4/8/2010 7:10 PM michieru
I solve this problem

this redirect the page

ScriptManager.RegisterStartupScript(Page, typeof(Page), "nameScript", "window.location.href='YourPage.aspx';", true);

this problem is because update panel and server.trasfer are not compartible (both) , don't working together.

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 5/19/2010 12:11 PM sudha
I also faced same .
when ever i deal with response obj , i come across some issue. almost i spent 2 hrs to solve this issue..

after adding
catch (System.Threading.ThreadAbortException ex)
{
}
this catch block in my code.
it works fine...
hope this ll save someones head. :D

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 5/22/2010 4:45 AM sc
use Response.Redirect("your url", false);

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 7/5/2010 3:16 AM asmcad
none of them worked for me: i don't knwo waht s wrong!!

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 8/12/2010 5:06 PM rabbit
what if you put the Response.Redirect(yourfile); in the finally block?

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 11/26/2010 3:02 PM selvaraj
Do it like this:
bool isAjax = false;
try
{
Response.Clear();
Response.Write(fnName());
Response.End(); // do not end the response here
isAjax = true;
}
catch()
{
//catch ur exception
}

finally
{
//check is Ajax request
if(isAjax)
Response.End();
}

Hope this will work

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 12/15/2010 1:23 AM Angel
Response.Redirect("nextPage.aspx",false);

Works great :)

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 12/27/2010 3:33 PM Arun
Finally Response.Redirect("nextPage.aspx",false); worked.




# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 1/27/2011 8:31 PM vadim
YES !!
...Response.Redirect("~/Contents/Public/ErrorPage.aspx", false);
worked for me too !!
thanx guys

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 5/2/2011 11:32 AM Pankaj Sharma
Follow this article it helped me.

http://support.microsoft.com/kb/312629/EN-US/

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 5/7/2011 3:27 PM Manish Srivastava
Use given below code

Response.Redirect("Success.aspx?evt=2", false);

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 5/16/2011 10:17 AM Kamal Deep Singh
Please use Response.Redirect("page1.aspx" , false);

This happens because you might be using http handlers

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 5/30/2011 12:36 PM Vuyiswa
When you are doing

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

Always use "False" to end response.

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 6/2/2011 3:37 PM Amit Gandhi
Use Response.Redirect("Success.aspx?evt=2",false); need to pass false param in try catch for Response.Redirect to supress Application_End event.



# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 6/6/2011 10:35 AM Mohd Owais
Pls try this

if (retVal == 0)
Response.Redirect("Success.aspx?evt=0",false);

if (retVal == -2) //Email-Id is already present
Response.Redirect("Success.aspx?evt=1",false);

if (retVal == -1) //Some error occured
Response.Redirect("Success.aspx?evt=2",false);

}

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 6/8/2011 4:44 PM HArmeet
try using
Response.Redirect("Success.aspx?evt=1",false);



# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 7/8/2011 2:50 PM Revathi
hi

U can use the end response overload of the Response.Redirect() method to avoid this error.

For ex,
Response.Redirect("nextpage.aspx",false);



# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 7/25/2011 4:33 PM zaigham sarfaraz
F.U.C.K you man. Why do you want to solve this problem. Lets live with this

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 8/20/2011 2:38 PM Praveen
Use over loaded function of response.redirect("xtz.aspz", false); this will work fine.

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 10/11/2011 4:42 PM Rakesh Lal Dewangan
Make second argument of response object is false, please check the code below
response.redirect(url,false);

Njoy.

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 10/12/2011 7:12 PM chandrasenachary
Response.Redirect("Success.aspx?evt=0" ,false);

add false in the second parameter.

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 10/21/2011 6:26 PM jyoti
http://support.microsoft.com/kb/312629/EN-US/
use this, this will surly helps you.

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 10/21/2011 6:27 PM jyoti
use this, this will surly helps you.
http://support.microsoft.com/kb/312629/EN-US/


# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 10/27/2011 3:53 PM Harish KV
Use Response.Redirect("Success.aspx?evt=1", false); in all the above cases

# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 11/2/2011 8:27 PM John MacIntyre
I've had similiar issues with try/catch blocks creating oddities. here's mine. http://whileicompile.com/?p=458

Now I'm getting the same problem as you did. pita!


# re: BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack. 3/15/2012 10:49 PM killerqx1
Hi all! i am tried use Response.Redirect("Success.aspx?evt=0" ,false); but why it not worked for me??? who can help me

Post A Comment
Title:
Name:
Email:
Website:
Comment:
Verification: