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

Posted by: Rick Strahls WebLog, on 10 Aug 2006 | View original

All of a sudden I’m getting this error message in my inbound Web Service that’s been working fine for several days:   Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack.   The Web Service just started failing all of a sudden, and I’ve been trying to back track what’s changed, but I can’t find anything wrong here.   The behavior that I’m seeing is mighty whacky: If I run in the debugger the code...

Advertisement
The leading UI suite for ASP.NET - Telerik radControls
Outstanding performance. Full ASP.NET AJAX support. Nearly codeless development.

Similar Posts

  • Web Control Developer Macro Goodness more
  • Programmatically Create Windows Workflow Rules more
  • ASP.NET Expressions — A Useful Feature more

News Categories

.NET | ADO.NET | Agile | Ajax | Architecture | ASP.NET | BizTalk | C# | Certification | Community Server | dasBlog | DataGrid | DataSet | Debugger | DotNetNuke | Events | GridView | IIS | Indigo | JavaScript | Mobile | Mono | Patterns and Practices | Performance | Podcast | Refactor | Regex | Security | Sharepoint | Silverlight | Smart Client Applications | Software | SQL | VB.NET | Visual Studio | W3 | WCF | WinFx | WPF | WSE | XAML | XLinq | XML | XSD