Best practice for defining exception handling and error logging in ASP.NET MVC applications?

In your typical MVC application, you have many layers.

Database level Model layer (possibly in the same package as the database) View / UI layer Controller level Business level

Where should exception handling or error reporting be handled if you need to create custom exceptions, interfaces, and models for reporting errors in a fairly complex MVC application?

+3
source share

All Articles