locked
N-Tier development error handling RRS feed

  • Question

  • I would like to find out more about error handling in n-tier development. I basically have an idea but would like to find out more about it. If anyone can help me with any links, code or personal opinion i would appreciate it. Should i put error handling in one single component and then have one instance of the component on each tier.


    Plus anything about Validation code. Should I have one component for that?
    • Edited by achurchill Tuesday, October 16, 2012 6:05 PM
    Tuesday, October 16, 2012 6:01 PM

Answers

  • Look at the Microsoft patterns & practices, including the code for it

    http://pauliom.wordpress.com

    • Marked as answer by achurchill Sunday, October 21, 2012 9:08 PM
    Saturday, October 20, 2012 10:44 AM

All replies

  • So much of it is "depends". E.g. If you centralise *all* the error handling will you want to split a component/servce out and re-use it somewhere else. Will that mean you carry a big monolithic error component full of unrelated information? If you have an error component but each of the other services owns its error messages then that wouldn't be a problem.

    http://pauliom.wordpress.com

    Friday, October 19, 2012 3:11 PM
  • Does anyone have any recommendations on books, or any links on code?
    Friday, October 19, 2012 10:49 PM
  • Look at the Microsoft patterns & practices, including the code for it

    http://pauliom.wordpress.com

    • Marked as answer by achurchill Sunday, October 21, 2012 9:08 PM
    Saturday, October 20, 2012 10:44 AM