System.IO.FileS ystemWatcher

[John Talli]

System.IO.FileS ystemWatcher

When a user copies and pastes a file from one directory to a directory that is monitored
by the FileSystemWatch er, the FileSystemWatch er executes twice, once for a CREATED file
event and once for a CHANGED file event.

I think I understand why. First the monitored file is created and then contents are
inserted into it. (Although the file datetime remains the same.)

This is not what I require. If there is a new file created in a monitored directoy, I
only want TRUELY CREATED event raised, not the default of CREATED event raised & CHANGED
event raised.

Is there anyway I can turn-off the second event (CHANGED event raise) ?

Thanks

[=?Utf-8?B?Tmljb2xhcw==?=]

Hi this is a bug from Microsoft in this Obj

''' <remarks>Implem enting a trick to stop double call from the onChange
FileSystemWatch er event bug</remarks>
Protected Sub OnChanged(ByVal source As Object, ByVal e As
FileSystemEvent Args)
Try

If lastChange <>
TimeSpan.FromTi cks(Now.Ticks). TotalMillisecon ds Then
'DO YOUR STUFF HERE
End If

lastChange =
TimeSpan.FromTi cks(Now.Ticks). TotalMillisecon ds

Catch ex As Exception
errorHandler(ex , Me.GetType.ToSt ring & ".onChanged ")

Finally
End Try

End Sub

Hope this help

Nicolas

"John Talli" wrote:

System.IO.FileS ystemWatcher

When a user copies and pastes a file from one directory to a directory that is monitored
by the FileSystemWatch er, the FileSystemWatch er executes twice, once for a CREATED file
event and once for a CHANGED file event.

I think I understand why. First the monitored file is created and then contents are
inserted into it. (Although the file datetime remains the same.)

This is not what I require. If there is a new file created in a monitored directoy, I
only want TRUELY CREATED event raised, not the default of CREATED event raised & CHANGED
event raised.

Is there anyway I can turn-off the second event (CHANGED event raise) ?

Thanks

[John Talli]

Thanks!!! I'll play with this and let everyone know the outcome. This double call is
an interesting feature from MS.
"Nicolas" <Ni*****@discus sions.microsoft .comwrote in message
news:87******** *************** ***********@mic rosoft.com...

Hi this is a bug from Microsoft in this Obj

''' <remarks>Implem enting a trick to stop double call from the onChange
FileSystemWatch er event bug</remarks>
Protected Sub OnChanged(ByVal source As Object, ByVal e As
FileSystemEvent Args)
Try

If lastChange <>
TimeSpan.FromTi cks(Now.Ticks). TotalMillisecon ds Then
'DO YOUR STUFF HERE
End If

lastChange =
TimeSpan.FromTi cks(Now.Ticks). TotalMillisecon ds

Catch ex As Exception
errorHandler(ex , Me.GetType.ToSt ring & ".onChanged ")

Finally
End Try

End Sub

Hope this help

Nicolas

"John Talli" wrote:

>System.IO.File SystemWatcher

When a user copies and pastes a file from one directory to a directory that is
monitored
by the FileSystemWatch er, the FileSystemWatch er executes twice, once for a CREATED
file
event and once for a CHANGED file event.

I think I understand why. First the monitored file is created and then contents are
inserted into it. (Although the file datetime remains the same.)

This is not what I require. If there is a new file created in a monitored directoy,
I
only want TRUELY CREATED event raised, not the default of CREATED event raised &
CHANGED
event raised.

Is there anyway I can turn-off the second event (CHANGED event raise) ?

Thanks