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

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?

New on Geeks with Blogs

Get the Size of a Directory in Linux the Easy Way

du -sh for the quick answer, ncdu for the cleanup, df for the disk itself: every command for checking directory size in Linux, plus why du and df never agree.

Vim Search and Replace: The Ultimate Guide

One :%s command replaces every match in a file before a find dialog would even open. The Vim substitute patterns worth the muscle memory: flags, ranges, capture groups, and multi-file edits.

Because of AI, You Need a New Development Team

Your existing team is buried in the complexity of your existing product. AI rewards the team with a blank slate. Most companies don't have one.

The Offshore Problem That Starts With a "Yes"

The stories about offshore "not working" are rarely about skill. They are about an invisible communication gap, and it starts the moment someone says yes.