如何在未知模块上分析System.AccessViolationException

Question

I have a MVC 4 project on Framework 4 with throws a System.AccessViolationException when you extend the HtmlHelper using HtmlHelper.ViewContext.Writer

The following code compiles just fine:

public static void Test(this System.Web.Mvc.HtmlHelper helper)
{
    System.IO.TextWriter writer = helper.ViewContext.Writer;
    writer.WriteLine("<b>Test Output</b>");
}

But when I use it in the view it throws the error. Now I've confirmed the DLL that causes the problem, but I have no idea what to look for, because the error message is not helpful, not even a stack trace. The thing is the project was a MVC3 project written on VS2010, now that I updated to VS2013 and tried to upgrade to MVC4 the problem started, but the weird thing is that when I used the same DLL on other MVC4 projects in VS2010 on Framework 4, then it worked, now when I made a clean MVC4 project on Framework 4 this happens.

I know that the DLL in question is causing the problem and I do have the source code for it, but I have no idea what to look for.

I did test other extending methods and for example this works just fine:

public static System.Web.Mvc.MvcHtmlString Test(this System.Web.Mvc.HtmlHelper helper)
{
    return new System.Web.Mvc.MvcHtmlString("<b>Test Output</b>");
}

So it has to do something with the ViewContext of the HtmlHelper , but what?

The easiest thing would be to simply change the extending method, but do to company policy I'm not allowed to do that so I need to figure this out.

My biggest issue is that the DLL in question is not really written by me and only my computer has VS2013, so any direction would be helpful ie what to look for or anything like that.

Answer 1

So after a lot of trial and error I accidental deleted one of my main MVC DLL from the main project. So I used the NuGet to restore the MVC4 there. Now I used the update to restore it and there you go... Solved.

The new MVC 4.0 version is 4.0.40804.0 If you are having the same problem as I did then simply update the MVC through NuGet and problem solved.