I've had several instances in which I was debugging my MVC application, and would get an error like:
Error executing child request for handler
I wrote about my distate for this ambiguous error message in another post. The problem is that there are many different things that can trigger this message. In another instance, I was returning ASP.NET Charts to a View programmatically. Most of the time it would work, sometimes the image tag the result was being sent to would just show up as a broken link. No exceptions thrown - just a silent failure. Gotta love that. Turned out that another developer had instantiated a repository class in a view model (ugh!), and sometimes it was still alive when the data context was used to retrieve the chart data.
So I looked all over for answers to these questions, and by accident came upon something I didn't know about, and thought I'd share for those with similar issues. In Visual Studio, if you click on 'Debug' and the click 'Exceptions', the Exceptions dialogue box appears. I just click the top-level checkbox for 'Common Language Runtime Exceptions' to select all of the options under that category. Once this is done, the application will throw an exception if any of the options there have an exception du
View Complete Post