CODEWITHSUNDEEP
.netasp.net-mvcmodel-view-controllererror-handlingglobal-asax
Zack Peterson
Zack Peterson

Reputation: 57343

ASP.NET MVC Error Logging in Both Global.asax and Error.aspx

I'm creating an ASP.NET MVC application. I need to handle exceptions in two places.

Global.asax.vb file:

Public Class MvcApplication
    Inherits System.Web.HttpApplication
    ...
    Sub Application_Error(ByVal sender As Object, ByVal e As EventArgs)
        LogException(HttpContext.Current.Server.GetLastError(), Request)
    End Sub
    Shared Sub LogException(ByVal ex As Exception, ByRef r As System.Web.HttpRequest)
        ...
    End Sub
End Class

Views\Shared\Error.aspx file:

<%@ Page Language="VB" Inherits="System.Web.Mvc.ViewPage(Of System.Web.Mvc.HandleErrorInfo)" %>
<script runat="server">
    Sub Page_Load(ByVal Sender As System.Object, ByVal e As System.EventArgs)
        MvcApplication.LogException(Model.Exception, Request)
    End Sub
</script>
...

But I get this error:

C:\inetpub\example.com\Views\Shared\Error.aspx(5): error BC30451: Name 'MvcApplication' is not declared.

Where should I define my LogException() function so that it is accessible from both the Global.asax.vb file and the Error.aspx file? Where is the most MVC-ish?

Upvotes: 3

Views: 6351

Answers (3)

Paulo Santos
Paulo Santos

Reputation: 11567

Actually for what I could gather you're only missing a directive:

<%@ Import Namespace="[Your default namespace]" %>

And it whould work as advertised.

Upvotes: 1

SideFX
SideFX

Reputation: 839

You may want to try an module called ELMAH. Scott Hanselman says "ELMAH is Tivo for your ASP.NET Errors". I've am currently using it for logging errors in my ASP .NET + MVC applications and it works like a charm. Setup was easy because all that is required is adding lines to the web.config. You can even restrict who has access to view the error logs.

http://www.hanselman.com/blog/ELMAHErrorLoggingModulesAndHandlersForASPNETAndMVCToo.aspx

Upvotes: 6

User
User

Reputation: 30945

The most MVC-ish way would be to use ActionFilters to handle (log) exceptions.

Check out this for example:

Logging with ASP.NET MVC Action Filters

Upvotes: 2

Related Questions