I used to edit and continue when an exception occurred in Visual Studio 2015 C # projects (WPF, if necessary). I often get simple things like null reference exceptions, and I could quickly fix the problem and continue.
However, lately I have been constantly receiving the following warning message:

"The debugger cannot relax in this frame."
He notes that unwinding is not possible in the following:
- Debugging was started using Just-In-Time debugging. - This is not so, I am debugging by running "Start Debugging" from Visual Studio.
- Now unwinding is taking place - not what I know about, if for some reason this does not always happen!
- A System.StackOverflowException or System.Threading.TreadAbortException - this occurs in all exceptions, including simple ones like Null Reference
There are several articles in my googling which say that they implemented this function in 2006, besides this, only about 3 results are returned!
This seems to be a specific project. In a new new project:
Object o = null; String s = o.ToString();
Throws an exception and allows me to edit and continue the line earlier. In my existing project, I canβt relax, and it causes a dialogue.
Edit: Tried it using another computer and installing Visual Studio and still has the problem.
There seems to be a problem with Caliburn Micro.
If I have a button on my user interface associated with an event in the code with the above code, I can rewind and debug it. However, if I use cal.message.attach and put the code in the ViewModel reference method, I cannot relax. But I'm not sure.
debugging c # visual-studio visual-studio-2015 caliburn.micro
Joe
source share