I have another ASP.Net web project that I work in, and I approached error handling from different angles. I'm just wondering if any experienced and experienced developers had any recommendations.
Bonus points for discussing a good journal structure for ASP.net :)
I used ELMAH (error logging modules and error handlers) - this is an application-level error logging tool that fully connects to several projects and works great: http://code.google.com/p/elmah/
ASP.NET 2.0: http://msdn.microsoft.com/en-us/library/ms998306.aspx
, . ErrorHandler.aspx, customErrors web.config, , , , , , .
System.Exception, -, ErrorHandler.aspx, FriendlyMessage.
Application_Error() . Application.Log(), .
Application.Log () can be configured using the web.config file to direct output to a file, server event log, etc.
In some cases, I also implemented my own logging using common TraceSource and a custom Listener that logged messages in the database table.
Source: https://habr.com/ru/post/1702777/More articles:Why should I specify all type type parameters? - genericsHow to store many product prices in a flexible way? - design-patternsShow changes since last "get latest version"? - version-controldisplay of # views on a page without getting into the database all the time - databaseHow to change webservice proxy to get Raw XML - c #What do you call ASHX from JavaScript? - javascriptIs it good to have two frameworks in one project? - javaC / C ++ CALL16 reloc linker in xxxxx not against global character - c ++asp.net 2.0 global themes not working on new Windows 2008 server - asp.netIs there a framework for dependency injection for poor / lazy designs? - designAll Articles