System File Watcher and networked drives

[Lilith]

Would I be correct in assuming that the system file watcher is only
valid for local drives and won't work for networked file system?

 

[Tom Porterfield]

Would I be correct in assuming that the system file watcher is only
valid for local drives and won't work for networked file system?

That would be an incorrect assumption. Per the Remarks section for the
FileSystemWatcher class:

Use FileSystemWatcher to watch for changes in a specified directory. You
can watch for changes in files and subdirectories of the specified
directory. The component can watch files on a local computer, a network
drive, or a remote computer.

 

[Lilith]

That would be an incorrect assumption. Per the Remarks section for the
FileSystemWatcher class:

Use FileSystemWatcher to watch for changes in a specified directory. You
can watch for changes in files and subdirectories of the specified
directory. The component can watch files on a local computer, a network
drive, or a remote computer.

Would the type of network matter, MS vs. NetWare?

I'm working on a program to monitor the content of a series of log
files that are created periodically with sequential extension numbers.
The files exist on a NetWare drive.

The program doesn't appear to work, whether I'm using a UNC path or a
mapped drive. If I point the program to a local drive and copy the
files from the NetWare drive into it, the program does detect the
"creation" and changes of these files.

 

[Ignacio Machin \( .NET/ C# MVP \)]

Hi,

Yes. IIRC it needs to be a NTFS share

 

[Lilith]

Hi,

Yes. IIRC it needs to be a NTFS share

Thanks. That's what I was afraid of. Now, where did I put that
drawing board?

 

[Michael D. Ober]

It needs to be an NTFS share on an NT4 or later system. NT 3.51 and earlier
did not support the File System Watcher across a network. Also, Samba
doesn't support it either.

Mike Ober.