Multiple FileSystemWatch ers, monitoring the same path

[Fredrik Johansson]

Hello,

I have built a .NET remoting solution (SingleCall) that writes a file to
disk, then waits for a second file in a specified folder (using the
FileSystemWatch er.WaitForChang ed method). When the component is called by two
peers at the same time, two FileSystemWatch ers are created (one for each
peer). They are both monitoring the same path (but for different files -
using different filters). The following code illustrates the scenario:

using System;
using System.IO;
using System.Threadin g;

class clsMain {
static void Main() {
Thread thread1 = new Thread(new ThreadStart(t1) );
Thread thread2 = new Thread(new ThreadStart(t2) );
thread1.Start() ;
thread2.Start() ;

Console.ReadLin e();
}

static void t1() {
FileSystemWatch er fs1 = new FileSystemWatch er(@"c:\files", "file1");
if (!fs1.WaitForCh anged(System.IO .WatcherChangeT ypes.All, 10000).TimedOut ) {
System.Console. WriteLine("f1 found!");
} else {
System.Console. WriteLine("f1 not found!");
}
}

static void t2() {
System.IO.FileS ystemWatcher fs2 = new
System.IO.FileS ystemWatcher(@" c:\files", "file2");
if (!fs2.WaitForCh anged(System.IO .WatcherChangeT ypes.All, 10000).TimedOut ) {
System.Console. WriteLine("f2 found!");
} else {
System.Console. WriteLine("f2 not found!");
}
}
}

When copying file1 and file2 to the path c:\files (which are monitored by
the two FileSystemWatch ers) only one of them receives a signal, the other one
simply timesout.

Please advice,
Best Regards,
Fredrik Johansson

[Fredrik Johansson]

I solved the problem by creating my own FileSystemWatch er (non-derived) and
thus, pulled the contents of a folder every n second.

"Fredrik Johansson" wrote:

Hello,

I have built a .NET remoting solution (SingleCall) that writes a file to
disk, then waits for a second file in a specified folder (using the
FileSystemWatch er.WaitForChang ed method). When the component is called by two
peers at the same time, two FileSystemWatch ers are created (one for each
peer). They are both monitoring the same path (but for different files -
using different filters). The following code illustrates the scenario:

using System;
using System.IO;
using System.Threadin g;

class clsMain {
static void Main() {
Thread thread1 = new Thread(new ThreadStart(t1) );
Thread thread2 = new Thread(new ThreadStart(t2) );
thread1.Start() ;
thread2.Start() ;

Console.ReadLin e();
}

static void t1() {
FileSystemWatch er fs1 = new FileSystemWatch er(@"c:\files", "file1");
if (!fs1.WaitForCh anged(System.IO .WatcherChangeT ypes.All, 10000).TimedOut ) {
System.Console. WriteLine("f1 found!");
} else {
System.Console. WriteLine("f1 not found!");
}
}

static void t2() {
System.IO.FileS ystemWatcher fs2 = new
System.IO.FileS ystemWatcher(@" c:\files", "file2");
if (!fs2.WaitForCh anged(System.IO .WatcherChangeT ypes.All, 10000).TimedOut ) {
System.Console. WriteLine("f2 found!");
} else {
System.Console. WriteLine("f2 not found!");
}
}
}

When copying file1 and file2 to the path c:\files (which are monitored by
the two FileSystemWatch ers) only one of them receives a signal, the other one
simply timesout.

Please advice,
Best Regards,
Fredrik Johansson