The Weird and The Wonderful

// Why return a "Foo" object type when we can just return a datatable? 
// We do have the type but unpacking it is just *so tiresome*. 
// As is writing a proper DAL or using one of the many free ORMs etc.
public DataTable GetFooByID(int memberID)//MethodID #210
{
  try
  {
    string query = "SELECT DISTINCT * FROM Foo WHERE bar=" + barId;// I hope we don't have little Bobby tables as a member!
    DataTable dt = Utils.ExecuteReader(query);
    //Because we just have too many processor cycles dagnammit:
    if (dt != null)
    {
       return dt;
    }
    else
    {
       return null;
    }
  }
  //Somebody has been reading a book about catch errors on database calls. 
  // Pity they didn't get to the advice about not catching all exceptions 
  catch (Exception ex)
  {
    // Why is it #210? Beacuse the comment next to the method declaration says it is, that's why!
    // No need to deal with pesky stack-traces  with their confusing line numbers or useful additions to the error message!
    throw new Exception("MethodID:= #210, Error:=" + ex.Message);
  }
}

foreach(MyfileInfo fil from files)
{
   switch (fil.MyFileType)
   {
      case A:
      //Do some work for file A
      break;

      case B:
      //Do some work for file B
      break; 
   }
}

foreach(MyfileInfo fil from files)
{
   switch (fil.MyFileType)
   {
      case A:
      //Do some work for file A
      break;

      case B:
      foreach(MyfileInfo fil2 from files)
      {
         switch (fil2.MyFileType)
         {
            case A:
            break;

            case B:
            //Do new work for File B.
            break;
         }
      }
      break
   }
}