Represents the method that will handle the System.ComponentModel.Design.IDesignerHost.BatchOperation event.
[Visual Basic] Public Delegate Sub BatchOperationEventHandler( _ ByVal sender As Object, _ ByVal e As BatchOperationEventArgs _ ) [C#] public delegate void BatchOperationEventHandler( object sender, BatchOperationEventArgs e ); [C++] public __gc __delegate void BatchOperationEventHandler( Object* sender, BatchOperationEventArgs* e );
[JScript] In JScript, you can use the delegates in the NGWS frameworks, but you cannot define your own.
The declaration of your event-handling method must have the same parameters as the BatchOperationEventHandler delegate declaration.
When you create a BatchOperationEventHandler delegate, you identify the method that handles the event. For an overview, see TBD.
To associate the event with your event-handling method, call the AddOn method of the IDesignerHost. The event-handling method is called whenever the event occurs, until you call the RemoveOn method of the control.
Note Delegates are the underlying mechanism for events, but most of the time you won't use them directly. For details, see TBD.
Batch operations can refresh multiple components at once. Batch operation methods provide a way to prevent performance and flicker problems by deferring expensive processing on multiple components until after the operation has completed. A System.ComponentModel.Design.IDesignerHost.BatchOperation event will occur upon first entry of a batch operation, and again upon last exit of the operation; nested calls do not generate events. Also, if the designer host is currently within a batch operation and an object adds an event handler, the handler will be invoked immediately.
Namespace: System.ComponentModel.Design
Assembly: System.dll
System.ComponentModel.Design Namespace | System.ComponentModel.Design.BatchOperationEvent