FileSystemWatcher on mapped network drive

c# exception-handling filesystemwatcher mapped-drive
Jess picture Jess · Jul 17, 2011 · Viewed 9.5k times · Source

Are there any special considerations (other than permissions) that you should take into account when implementing a FSW to monitor a mapped network drive. Will the FSW throw an exception if the drive loses its connection? If not (or if I just catch/handle that exception), will it be sufficient to poll the DirectoryInfo.Exists property to verfity the connection?

Answer

Jalal Said picture Jalal Said · Jul 17, 2011

Well, I have used the FileSystemWatcher to monitor a shared folder that exists on another computer in the network, and here is my experience:

  1. You can check the connection via File.Exists or Folder.Exists.
  2. The FileSystemWatcher will not throw an exception if the you lose connection to that shared folder. Instead, whenever the connection is lost you will get this error message: "The specified network name is no longer available". When you get that error, the FSW will no longer handle any data even if the connection is reestablished, so handle FileSystemWatcher.Error event and if the error is raised, reset EnableRaisingEvents to true again, or reinitialize the FSW

Related questions

File access error with FileSystemWatcher when multiple files are added to a directory

I am running into an issue with a FileSystemWatcher when multiple files are placed into the watched directory. I want to parse the file as soon as it is placed in the directory. Typically, the first file parses fine, but …

Read More
Get connection string from App.config

var connection = ConnectionFactory.GetConnection( ConfigurationManager.ConnectionStrings["Test"] .ConnectionString, DataBaseProvider); And this is my App.config: <?xml version="1.0" encoding="utf-8" ?> <configuration> <connectionStrings> <add name="Test" connectionString="Data Source=.;Initial Catalog=OmidPayamak;Integrated Security=True" …

Read More
Catch multiple exceptions at once?

It is discouraged to simply catch System.Exception. Instead, only the "known" exceptions should be caught. Now, this sometimes leads to unneccessary repetitive code, for example: try { WebId = new Guid(queryString["web"]); } catch (FormatException) { WebId = Guid.Empty; } catch (OverflowException) { WebId = …

Read More