Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>While I'm not sure why this happens (I also can't reproduce this) I might have some fixes that you might try. The WebPageHttpModule (in System.Web.WebPages) is supposed set AppStartExecuteCompleted but it doesn't, and that's why you get an exception (All this guess work is based on that).</p> <p>So... Looking around the source code I <em>BELIEVE</em> that the source of this bug is something fishy with the Web Development Server and PreApplicationCode + dynamic registration of a module (WebPageHttpModule). The Module init should ALWAYS run at the application start, but for some reason I <em>GUESS</em> that it doesn't. Maybe someone can somehow test it.</p> <p>Some fixes that I thought about (again, this is pure guess work as I can not reproduce this).</p> <p>1) try to register the WebPageHttpModule module statically in the WebConfig. <em>update</em> I've tested this, and this doesn't throw an exception. However, it registers TWO httpmodules.</p> <p>2) According to the comments on that thread you've linked it appears that this doesn't happen on IIS, so I would try to run under IIS Express (under VS 2010 SP1).</p> <p>As I said before, this is just guess work. There could be other reasons for module not to run... Such as the Web Server not restarting properly, including some problem with the PreApplicationCode, or not resetting s_appStartExecutedLock to false in the HttpModule, or something wierd with the HttpContext.Items which could ALSO cause the module not to run... </p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload