Try It - Catch Return Strategy

Question

When used try-catchin methods, if you want the application to continue even if errors occur, is it normal to return the default value as a return through the catch block and register an error for later viewing?

Example:

public static string GetNameById(int id)
{
    string name;
    try
    {
        //Connect to Db and get name - some error occured
    }
    catch(Exception ex)
    {
        Log(ex);
        name = String.Empty;
    }

    return name;
}

Example 2:

public static string GetIdByName(string name)
{
    int id;
    try
    {
        //Connect to Db and get id- some error occured
    }
    catch(Exception ex)
    {
        Log(ex);
        id = 0;
    }

    return id;
}

Is it possible to return any default value (depending on the type of method return ... ???) so that the application logic, which required the result from this method, does not fail and keeps going ....

Thanks in advance...

Sincerely.

Answer 1

, , - (, , , ..). , - .

- - :

public static string GetNameById(int id)
{
    string name;
    try
    {
        //Connect to Db and get name - some error occured
    }
    catch(Exception ex)
    {
        Log(ex);
        throw; // Re-throw the exception, don't throw a new one...
    }

    return name;
}

, - .

, , , , , , , , , . " ", SO.com .

Answer 2

, . , , . ( ).

TryGet, :

public static bool TryGetNameById(int id, out string name) 
{ 
    try 
    { 
         //Connect to Db and get name - some error occured
         name = actualName
         return true; 
    } 
    catch(Exception ex) 
    { 
        Log(ex); 
        name = String.Empty; 
        return false;
    }  
} 

, . , . -, , , -.

Answer 3

: .

- , .

, , . , .

" " , CPU , .

, . , , .

- : PostSharp? , .

Answer 4

, , . , , . / , .

, , , , , - , .

, , . - , / , .

Answer 5

, , .

: "log the exception part", , ( ?)

, - swalowing, , .

Answer 6

. , , , , ...

catch, , , catch .

, , , "" , , , , , .

, , , , ...

Answer 7

, . , , , - - .

: , , .

Answer 8

, , ... , "Can not Login", SqlException .

, ... , , 100% , , , , .. : http://blogs.msdn.com/b/larryosterman/archive/2005/05/31/423507.aspx. : http://blogs.msdn.com/b/oldnewthing/archive/2011/01/20/10117963.aspx

Answer 9

try/catch , , .

. , , , .

, , , , / .

Answer 10

. : i, , , . Soemtiems . .

, " " , . (, ). , (T) maeks.

, 99% . 1% .

Answer 11

, " ".

. - , , .

. , , (, getSecurityGroup), , , , - , .

, , . - , , , ... .

, , , , , .

In fact, as a rule, at any time when you catch an error, you have to think a lot about whether the error is valid, and the continuation is valid or is it a stop show error, and you just have to refuse.