FileSystemWatcher on a network drive that gets disconnected

[Adam Clauss]

I have a FileSystemWatcher which I have listening on a network path
(\\server\foldername). I have events wired for files being created and
changed.

I have noticed that if the connection to the path is lost (I can easily
simulate this by pulling the network cable on the fileshare host) that I no
longer receive events. Is there anyway to detect this and recover from it?

Thanks!

 

[Willy Denoyette [MVP]]

I have a FileSystemWatcher which I have listening on a network path
(\\server\foldername). I have events wired for files being created and
changed.

I have noticed that if the connection to the path is lost (I can easily
simulate this by pulling the network cable on the fileshare host) that I
no longer receive events. Is there anyway to detect this and recover from
it?

Thanks!

If your client is directly wired to the server, you could use
System.Management and WMI to watch for "MSNdis_MediaConnectStatus" events,
drop the FileSystemWatcher when a disconnected event arrived and re-create
the FSW after a "connected" event arrived.
However, if you are on a switched network, there is little you can do other
than trying to open a temp. file on the share you are watching at a regular
interval, when this fails you drop the FSW and re-create him back when the
share reconnects.

Willy.

 

[Eric Moreau]

Hi

Have a look at an article I wrote in April 2005 at http://emoreau.s2i.com/

--


HTH

Éric Moreau, MCSD, Visual Developer - Visual Basic MVP
(http://aspnet2.com/mvp.ashx?EricMoreau)
Conseiller Principal / Senior Consultant
Concept S2i inc. (www.s2i.com)
http://pages.videotron.com/emoreau/

 

[Adam Clauss]

Thanks to both for your replies - I will look into both of these. If Eric's
works successfully, it does seem like the simpler of the solutions.

 

[Willy Denoyette [MVP]]

I did not try Eric's code, but there are a few things I don't like about it.

Willy.