By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
432,537 Members | 1,743 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 432,537 IT Pros & Developers. It's quick & easy.

System File Watcher and networked drives

P: n/a
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?

--
Lilith
Dec 6 '07 #1
Share this Question
Share on Google+
5 Replies


P: n/a
Lilith wrote:
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.
--
Tom Porterfield
Dec 6 '07 #2

P: n/a
On Thu, 06 Dec 2007 12:37:12 -0500, Tom Porterfield
<tp******@mvps.orgwrote:
>Lilith wrote:
>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.
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.

--
Lilith
Dec 6 '07 #3

P: n/a
Hi,

Yes. IIRC it needs to be a NTFS share

--
Ignacio Machin
http://www.laceupsolutions.com
Mobile & warehouse Solutions.
"Lilith" <li****@dcccd.eduwrote in message
news:45********************************@4ax.com...
On Thu, 06 Dec 2007 12:37:12 -0500, Tom Porterfield
<tp******@mvps.orgwrote:
>>Lilith wrote:
>>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.

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.

--
Lilith

Dec 6 '07 #4

P: n/a

On Thu, 6 Dec 2007 13:52:06 -0500, "Ignacio Machin \( .NET/ C# MVP \)"
<machin TA laceupsolutions.comwrote:
>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?

--
Lilith
Dec 6 '07 #5

P: n/a
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.
"Ignacio Machin ( .NET/ C# MVP )" <machin TA laceupsolutions.comwrote in
message news:e7**************@TK2MSFTNGP03.phx.gbl...
Hi,

Yes. IIRC it needs to be a NTFS share

--
Ignacio Machin
http://www.laceupsolutions.com
Mobile & warehouse Solutions.
"Lilith" <li****@dcccd.eduwrote in message
news:45********************************@4ax.com...
>On Thu, 06 Dec 2007 12:37:12 -0500, Tom Porterfield
<tp******@mvps.orgwrote:
>>>Lilith wrote:
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.

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.

--
Lilith




Dec 7 '07 #6

This discussion thread is closed

Replies have been disabled for this discussion.