Used too, when there was a runtime error the ide would break at the line that caused the problem. Now I'm thrown into some assembly code with the error
System.Windows.Markup.XamlParseException was unhandled
Message='The invocation of the constructor on type 'Main.MainWindow' that matches the specified binding constraints threw an exception.' Line number '4' and line
Which is extremely uninformative and inefficient. I can look down the chain to find the error thrown but this still is not very informative. How the heck can I get it back to the way it used to be?
This has something to do with wpf and the assembly code has System.Windows.Markup.XamlReader.RewrapException as the address. I spend anywhere from 10x to 10000x as long because of this. If the code is simple then I still have to read the error code and click
a button which takes time.
Also, I'd rather it break on the line and quit the process as it used to do. I don't need JIT debugging.
View Complete Post