Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have inherited an ASP.NET MVC2/VS2010 solution from a previous developer. In playing around with it I quickly realized that any and all server errors are not being displayed as such. They seem to be getting consumed and then a bunch of garbage text appears on the screen.
I’m not sure how this was managed, or where to even start looking for something like this. Has anyone experienced this before that could offer some insight into where to start looking?
Thanks.
In MVC errors are often caught using the HandleErrorAttribute. This can be apply at the controller or action level. The fact that you’re seeing garbage has me a little concerned as normally this attribute generates a generic error view (which you can customize). I wonder if you’ve got content type mismatches with some AJAX code — you might want to use Firefox with Firebug or the IE developer tools to catch the requests in flight and see the request/response headers and response content.