I have an asp.net 4.5 web forms project that's now under the asp.net one architecture (so we're integrating MVC in a few parts).
I am attempting to add Elmah to this setup. My goals are:
However, when I add the Elmah package via nuget, it does not appear to make any modifications to web.config. So, when I browse to /elmah.axd, I see:
Path '/elmah.axd' was not found. System.Web.HttpException (0x80004005): Path '/elmah.axd' was not found. at System.Web.HttpNotFoundHandler.ProcessRequest(HttpContext context) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
This makes sense, because web.config hasn't been modified to add the handlers.
However, adding elmah.axd does give us an MVC route. However, my instincts and some rudimentary tests tell me that these only cover errors within the purview of MVC.
it could be related to the existing sections/elements of your original web.config file, so that the web.config.transform in the Elmah package could not perform some of the add operations.
This document - http://docs.nuget.org/docs/creating-packages/configuration-file-and-source-code-transformations described explicitly what the Elmah package transformation will do, for web.config before and after.
Well this happened to me too, I did 3 things.
And after that my web config is updated and everything runnning smoothly.
User contributions licensed under CC BY-SA 3.0