I’ve just pushed new version of ELMAH.MVC NuGet package - 2.0.1. It covers some interesting parts, that I can’t wait to share.
For quite a while, I’ve been asked to provide VB.NET support. Originally, ELMAH.MVC was shipped as singe .cs file, that would not possible to use in VB.NET project at all. VB.NET support were planned for 2.0, but unfortunately it did not happen. I’ve just tested 2.0.1 and it works great with VB.NET, so all VB.NET developers - you are welcome to use it.
Another demanded feature was to provide custom path to ELMAH controller. By default ELMAH is available under
/elmah, which is nice, but sometimes you what to have a freedom to change it. It’s now possible,
web.config has additional configuration section,
<add key="elmah.mvc.route" value="elmah" />. By setting up elmah.mvc.route parameter, you can tweek a default one, like
<add key="elmah.mvc.route" value="secure/admin/errors" /> for instance.
ELMAH.MVC does not depend on WebActivator any longer. I’ve removed
App_Start.cs code and used PreApplicationStartMethodAttribute attribute. That allows to make a package more tiny + actually made it possible to avoid separate NuGet package for VB.NET projects.