Menu
▾
▴
#19 configSection and exceptionHandlers
This patch will use a configuration-section insted of
appSettings. (Only .Net 2.0, wrapper around the old
one to simplify code for .Net 1.x) Settings for .Net
1.x will bee handled by the default appSettings.
New parameter is added, exceptionHandlers. You can
implement ypr own exceptionHandlers, example logging
all exceptions handled by anthem to log-file
(Only .Net 2.0)
New interface to implement for the exceptionHandlers,
Anthem.IExceptionHandler.
Updated patch
Logged In: YES
user_id=1245761
What advantages does a configuration section have over
AppSettings for Anthem? One of the specific advantages of
Anthem over other libraries (like Atlas) that I have heard
is the ease of deployment. It seems like a configuration
section increases the complexity of deployment.
Logged In: YES
user_id=729250
Andy is right - one of the biggest benefits of the
Anthem.Net library is easy of use and deployment. I say, if
it ain't broke, don't fix it.
Cheers.
Logged In: YES
user_id=1487950
My problem was when I built this sectionHandler was logging
of errors. When I use anthem in production-environment, I
will not have a javascript-based errorhandler, I will have
the errors writes down to disc. Other pages I write will
global.asax (Application-OnError-method) take care of
errors and write the information down to disc. On anthem-
pages (with callback) handle Manager.OnError-method the
error and clear errors after the error have been returned
to client. Have you some better way to implement this
exceptionHandlers?
//P
Logged In: YES
user_id=1245761
A production Anthem error handler sounds like a great
idea. Someone on the forums proposed a similar idea also
as an HttpModule,
http://forums.anthemdotnet.com/forums/viewtopic.php?t=561
Perhaps the two proposed error handlers can be merged to
come up with a really great solution.
I'm not convinced the section handler is a good patch
though. Let's wait on that part until it becomes necessary.