Re: After adding ELMAH and changing elmah.mvc.route the old route is still available

[James_2JS]

Hi Adam,

You don't give any explanation of how you have actually done this integration!

However, I'm guessing that you've used Alexander Beletsky's NuGet package.

That being the case, I suggest you contact Alexander directly for support with this issue!

If I've got it wrong, could you supply further details please?

Cheers,

James

On Thursday, February 14, 2013 10:02:46 PM UTC, Adam Fridental wrote:

I've added ELMAH to my ASP.NET MVC 4 .Net 4 web application.

The intergration was simple and it works well.

I've changed the "elmah.mvc.route" value in the app settings of my web.config to an "Admin/SiteLog" route - the elmah log is displayed at this route now

But, it is also still shown at "/elmah" for some reason (with no css styling, but same content).

How can I disable the default elmah route?

[Adam Fridental]

You're right, I did use Elmah.MVC nuget package. I will try contacting him,

[Kevin Babcock]

In case you (or someone else) still need this answer...

In the appSettings section of web.config: the "elmah.mvc.IgnoreDefaultRoute" setting must be false if you do not wish an "/elmah" route to be added to your MVC application. Simply adding your own custom route does not prevent the default route from being added. Here are my settings (without other Elmah.MVC3 settings omitted for brevity):

<appSettings>
    <add key="elmah.mvc.route" value="error-logs" />
    <add key="elmah.mvc.IgnoreDefaultRoute" value="true" />
</appSettings>