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 hanselman.com/blog/ELMAHErrorLoggingModu....
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. hanselman.com/blog/ELMAHErrorLoggingModu....
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.
We have quite a log of Autofac and Nbernate set up in _start and if anything goes wrong and throws an error, an ActionFilter will never catch that error. Careful! – Perhentian May 7 '10 at 14:55 1 That example seems to be about logging actions, rather than logging exceptions – codeulike Oct 3 '10 at 18:28.
Actually for what I could gather you're only missing a directive: And it whould work as advertised.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.