[CLOSED] Randomly Displaying Warning Message - The web.config file for this project is missing the required AjaxRequestModule

[jcarlos]

Hi, I am developing a project using Ext.Net.MVC / Razor engine since a months ago.
Besides the very poor performance in the design mode of the views (.cshtml / razor) when using the components of the Ext.Net.MVC and some delay caused by the dynamic compilation of the views to be rendered in their first request, the application is running relatively well.
The main problem is that the application is randomly (< 1% of requests) displaying the warning message:

"The web.config file for this project is missing the required AjaxRequestModule."

In addition, all the extjs generated script code rendered by Ext.Net is being displayed in the client browser.
It appears that the message is being displayed when the application is in the phase of initialization, but it will not always occur and I cannot find a way to reproduce it.
It is important to emphasize that the "DirectRequestModule" was/is configured in web.config by the installation of the Ext.Net package.
What could be the cause and how can I prevent it?
Is there another elegant way to treat this case (i.e. internal error 500) instead of displaying the script source code and a message to the end user?

Best regards, thanks,

Jos? Carlos.

[geoffrey.mcgill]

In addition, all the extjs generated script code rendered by Ext.Net is being displayed in the client browser.

This is very strange. I don't ever remember running across this kind of problem before.

I will discuss with the Dev Team and we'll get back to you with any questions.

[Daniil]

I feel it might be a problem with a host server.

[Vladimir]

The main problem is that the application is randomly (< 1% of requests) displaying the warning message:
"The web.config file for this project is missing the required AjaxRequestModule."

Please update from SVN and retest, the issue should be fixed now

Besides the very poor performance in the design mode of the views (.cshtml / razor) when using the components of the Ext.Net.MVC and some delay caused by the dynamic compilation of the views to be rendered in their first request, the application is running relatively well.

Design mode is totaly inder VS control, Ext.Net doesn't execute any logic during design mode

[jcarlos]

Please update from SVN and retest, the issue should be fixed now

Hi Vladimir, sorry for the delay on the feedback, I didn't see your response.
Anyway, I updated to the last version from the Nuget (2.5.1) some weeks ago. Is this release updated with this fix?
I'm not certain on this but seems that the message about the web.config it is not displayed anymore but the issue about displaying the source code is still happening.
I implemented an IExceptionFilter and could get the entire exception tracing message as below:

  <Type>System.ObjectDisposedException</Type>
  <Message>Cannot write to a closed TextWriter.</Message>
  <Source>mscorlib</Source>
  <StackTrace>   at System.IO.__Error.WriterClosed()
   at System.IO.StringWriter.Write(String value)
   at System.Web.HttpResponseWrapper.Write(String s)
   at Ext.Net.MVC.PartialViewResult.RenderScript(ControllerContext context, String script)
   at Ext.Net.MVC.PartialViewResult.RenderRazorView(ControllerContext context, RazorView razorView)
   at Ext.Net.MVC.PartialViewResult.ExecuteResult(ControllerContext context)
   at System.Web.Mvc.ControllerActionInvoker.InvokeActionResult(ControllerContext controllerContext, ActionResult actionResult)
   at System.Web.Mvc.ControllerActionInvoker.InvokeActionResultFilterRecursive(IList`1 filters, Int32 filterIndex, ResultExecutingContext preContext, ControllerContext controllerContext, ActionResult actionResult)
   at System.Web.Mvc.ControllerActionInvoker.InvokeActionResultFilterRecursive(IList`1 filters, Int32 filterIndex, ResultExecutingContext preContext, ControllerContext controllerContext, ActionResult actionResult)
   at System.Web.Mvc.ControllerActionInvoker.InvokeActionResultFilterRecursive(IList`1 filters, Int32 filterIndex, ResultExecutingContext preContext, ControllerContext controllerContext, ActionResult actionResult)
   at System.Web.Mvc.ControllerActionInvoker.InvokeActionResultFilterRecursive(IList`1 filters, Int32 filterIndex, ResultExecutingContext preContext, ControllerContext controllerContext, ActionResult actionResult)
   at System.Web.Mvc.ControllerActionInvoker.InvokeActionResultWithFilters(ControllerContext controllerContext, IList`1 filters, ActionResult actionResult)
   at System.Web.Mvc.ControllerActionInvoker.InvokeAction(ControllerContext controllerContext, String actionName)</StackTrace>

Seems that the Ext.Net is trying to write the script to a closed writer.

Could you evalute this, please?

Regards,

Jose Carlos.

[Vladimir]

Your stack trace shows that exception occurs inside PartialViewResult
So, we need test case which demonstrates how do you work with PartialViewResult and that case should reproduce the issue