Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
SynchronizingObject Property

FileSystemWatcher.SynchronizingObject Property

Gets or sets the object used to marshal the event handler calls issued as a result of a directory change.

Namespace:  System.IO
Assembly:  System (in System.dll)

[BrowsableAttribute(false)]
[IODescriptionAttribute("FSW_SynchronizingObject")]
public ISynchronizeInvoke SynchronizingObject { get; set; }

Property Value

Type: System.ComponentModel.ISynchronizeInvoke
The ISynchronizeInvoke that represents the object used to marshal the event handler calls issued as a result of a directory change. The default is null.

When SynchronizingObject is null, methods handling the Changed, Created, Deleted, and Renamed events are called on a thread from the system thread pool. For more information on system thread pools, see ThreadPool.

When the Changed, Created, Deleted, and Renamed events are handled by a visual Windows Forms component, such as a Button, accessing the component through the system thread pool might not work, or may result in an exception. Avoid this by setting SynchronizingObject to a Windows Forms component, which causes the methods that handle the Changed, Created, Deleted, and Renamed events to be called on the same thread on which the component was created.

If the FileSystemWatcher is used inside Visual Studio 2005 in a Windows Forms designer, SynchronizingObject automatically sets to the control that contains the FileSystemWatcher. For example, if you place a FileSystemWatcher on a designer for Form1 (which inherits from Form) the SynchronizingObject property of FileSystemWatcher is set to the instance of Form1.

.NET Framework

Supported in: 4.6, 4.5, 4, 3.5, 3.0, 2.0, 1.1

.NET Framework Client Profile

Supported in: 4, 3.5 SP1
Show:
© 2015 Microsoft