c# - try catch bad form? -

I think I know this type of answer, but there are always many ways of working (some of which Clearly incorrect :)) ...

I have a small random task to identify an employee manager. It is being used in an import script and it may be that the person's The immediate manager was left (disabled) so that we must find out that the employee The Ri (Manager) Manager (and so on) so we can assign them stuff that is not clear, the staff turned off the toll is a general list of employees that have been marked as unable to import.

I think what I am really asking is this: To create an example to create an exception to hold an overhead is overhead. And am I doing it differently? It works fine, but it seems that this is a bad form ..

I have a code like this:

  Get a private gridMinebold manager area (online employee employee) {Employee manager; {// See if the manager's manager is in the disabled list or not. Manager = (Please allow EMP in the employee where emp.EmployeeID.Equals (e.ManagerID)). Single (); // Yes, they are, therefore it is necessary to retrieve it IMEEnabledManagersID (Manager); } Hold {returns e.ManagerID; Excluding Recursion, you can probably just use  SingleOrDefault  

and Trial for the Null Actually, you probably do not need a full employee object - you can be enough just by returning the ID (fill), i.e.

  Private Gide Late Management ID (Guid ManagerId) {Var disabled = (Emp.EmployeesToDisable in emp where emp.EmployeeID == select managerId (Guid?) Emp.ManagerID) .SingleOrDefault (); Faucet reflex ==? ManagerId: getMyEnabledManagersID (disabled.Value); }  

In fact, basically I have the biggest concern that it is not specific to the type of the exception; It can be "thread block", "zombie connection", "deadlock", etc.