C#: Catching and handling Path Too Long Exception

You can use specify exception:
Try this:

try
     {
      FileInfo FI = new FileInfo(file);  // exception  is still raised 
      // Do Stuff with FI
     }
   catch(System.IO.PathTooLongException exception)
     {
       //Do nothing
          continue; 
     }

Select allOpen in new window

OK I'll give it a go I thought by not specifying the exception it would capture all exceptions?

BTW  I won't do nothing but will create a error log

Hi

I moved the "try" thus

                try
                {
                    string[] Files = Directory.GetFiles(folder);
                        int FilesCount = Files.Length;

                        if (FilesCount >=1)
                        {

                
                            foreach (string file in Files)
                            {
                                Console.WriteLine("File " + file);
                                // string NewFile = "";

                                FileInfo FI = new FileInfo(file);
                                // Do Stuff with FI

                            }
                    }
                }
                catch (Exception)
                {

                    ErrorLog += "Folder to long " + folder + "\n";
                    continue;
                }

Select allOpen in new window

This worked How might I capture the Exception reason and print this to the ErrorLog ?

Use type of Exception!

 catch(System.IO.PathTooLongException exception)
     {
      ErrorLog  += exception.Message;
     }

Select allOpen in new window

This is the documentation about exception including example code:
https://msdn.microsoft.com/en-us/library/system.exception(v=vs.110).aspx

catch (Exception e)
{
//use e.Message or e.ToString() or .... here to log what went wrong
}

Hi
Thanx for the link is  my understanding correct you use try / catch blocks where the code may encounter non program logic errors and nest 1 try within another something  like bellow?

Where looping through directories is the first try block this has 2 possible exceptions, Access denied and everything else
and have a second try / catch block to handle problems with files

I assume you handle every possible exception in it's own catch unless like here you handle every problem with a file the same

try{
    string[] folders = Directory.GetDirectories(BaseFold, "*", SearchOption.AllDirectories);

    // Do stuff with the folder
    foreach (string folder in folders)
    {
    try{
        string[] Files = Directory.GetFiles(folder);
        int FilesCount = Files.Length;
        // This is program logic therefore not an exception  
        if (FilesCount >=1)
        {

                
          foreach (string file in Files)
           {
              
             Console.WriteLine("File " + file);
             FileInfo FI = new FileInfo(file);
             // Do Stuff with FI

           }
         }
    }
    catch (Exception e)
    {
        // Log Error with a file
    //use e.Message or e.ToString() or .... here to log what went wrong
    }
    
    
    
    }
}
    catch (UnauthorizedAccessException ex)
    {
        // ok, so we are not allowed to dig into that directory. Move on.
        continue;  
    }
catch (Exception e)
{
 // Log all other Errors with directory
//use e.Message or e.ToString() or .... here to log what went wrong
continue;
}

Select allOpen in new window

Yes, try catch is for handling unexpected problems.

@AndyAinscow with ref to last comments I was referring to the logic of using nested Try /catch 1 for handling directories 2 for files I'm guessing there is no right or wrong answer or best practice
Anyway thanx for your help

Depends on the circumstances and just what you want.  No general answer that covers all cases.

For that I'd just use one try catch - because it is all to do with processing those folders.  However one could make a case for two try catch  blocks.