C # Creating an error checking class?

Question

I am very new to OOP, and in the program I'm working on, I have a Utilities class that contains some common methods. Should I include my error checking in the Utility class or should I create a new class only for error checking?

Answer 1

Utilities Utilities usually have the unpleasant habit of becoming monsters - keep the error checking code separate.

Answer 2

, , , Utilities. - , ().

, , OOP . , . "".

Answer 3

, , , (.. ). , .

public static class Utility
{
    public static string GetSomeString(string someOtherString)
    {
        try 
        {
            // something
        }
        catch (exception ex) 
        {
            // handle error
        }
        return result;
    }
}

Answer 4

. , , , .

, , Log4Net, AOP, , PostSharp.

Answer 5

, , , , . , , . internal.

Answer 6

Application_Error Global.asax? , .

Answer 7

id jsut ... , , EG , , ... ints ... end , . , ...

.

.

debug.assert - .

, . , .

iinstance WCF . IErrorHandler iirc , , , -, , , . , - , . , , . - ... , , , , .

- .

, . WCF, , , , ( ).

, , , .

, ... , , .

This view goes beyond OOP to more architectural issues — you need to know why you want to move the code to the utility class, and then you need to decide if you just need to put it ... I would suggest pulling it out well, but you should go further and think of error management as your own decision. His begging to solve the SOA style (or at least the project) imo .... its one of those things that is not only common in applications, but also invariant ....