Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Languages / C# / December 2007

Tip: Looking for answers? Try searching our database.

System File Watcher and networked drives

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Lilith - 06 Dec 2007 17:27 GMT
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?

Signature

Lilith

Tom Porterfield - 06 Dec 2007 17:37 GMT
> 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.
Signature

Tom Porterfield

Lilith - 06 Dec 2007 17:48 GMT
>> 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?
[quoted text clipped - 6 lines]
>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.

Signature

Lilith

Ignacio Machin ( .NET/ C# MVP ) - 06 Dec 2007 18:52 GMT
Hi,

Yes. IIRC it needs to be a NTFS share

Signature

Ignacio Machin
http://www.laceupsolutions.com
Mobile & warehouse Solutions.

>
>>> Would I be correct in assuming that the system file watcher is only
[quoted text clipped - 18 lines]
> files from the NetWare drive into it, the program does detect the
> "creation" and changes of these files.
Lilith - 06 Dec 2007 19:16 GMT
On Thu, 6 Dec 2007 13:52:06 -0500, "Ignacio Machin \( .NET/ C# MVP \)"
<machin TA laceupsolutions.com> wrote:

>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?

Signature

Lilith

Michael D. Ober - 06 Dec 2007 23:58 GMT
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.

> Hi,
>
[quoted text clipped - 21 lines]
>> files from the NetWare drive into it, the program does detect the
>> "creation" and changes of these files.

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.