{"id":107,"date":"2005-09-26T00:00:00","date_gmt":"2006-05-09T00:00:00","guid":{"rendered":"https:\/\/test.simple-talk.com\/uncategorized\/custom-events-in-vb-net-2005\/"},"modified":"2021-05-17T18:36:52","modified_gmt":"2021-05-17T18:36:52","slug":"custom-events-in-vb-net-2005","status":"publish","type":"post","link":"https:\/\/www.red-gate.com\/simple-talk\/development\/dotnet-development\/custom-events-in-vb-net-2005\/","title":{"rendered":"Custom Events in VB.NET 2005"},"content":{"rendered":"
\n

Creating custom events with Visual Basic .NET 2005<\/h2>\n

Events model in VB.NET<\/h2>\n

Events are defined as actions or occurances of interest. An interested object can subscribe to an event and be notified when it happens. For example, a button on a form can generate a click event and the form can subscribe and get notified when the event occurs. This click event is processed through the form code.<\/p>\n

VB.NET 2005 provides a range of flexible event models to address simple or very complex events. Below is an example of a simple event using a Worker <\/i>class with a DoWork<\/i> method:<\/p>\n

  Public Class Worker  \n    Public Sub DoWork()  \n      For completedWork As Integer = 1 To 100  \n        System.Threading.Thread.Sleep(1000) \n        Console.WriteLine(completedWork) \n \n      Next \n    End Sub  \n  End Class <\/pre>\n
The DoWork<\/i> method has a For <\/i>loop repeating 100 times, waiting one second between loops, and printing out the completed work to the console. But a client such as a form using the object of the above class, for example, should provide visual feedback on how much work has been completed when the DoWork <\/i>method is called. Adding an event to the Worker <\/i>class and altering the DoWork<\/i> method to call the event can provide this information to the client.<\/p>\n
 Public Class Worker \n \n    Public Event WorkDone(ByVal completedWork As Integer)  \n    Public Sub DoWork() \n \n      For completedWork As Integer = 1 To 100  \n        System.Threading.Thread.Sleep(1000)\n        RaiseEvent WorkDone(completedWork) \n        Console.WriteLine(completedWork) \n \n      Next  \n    End Sub  \n  End Class  <\/pre>\n
An event called WorkDone<\/i> has been identified with an integer argument through which the amount of work completed can be passed. And in the DoWork<\/i> method, the event passing the actual amount of work completed is raised. Now the above class can be consumed by a client by declaring and creating a Worker <\/i>class object with events and handling the WorkDone <\/i>event to provide feedback on progress.<\/p>\n
Private WithEvents mWorker As New Worker \nPrivate Sub work_WorkDone(ByVal completedWork As Integer) Handles mWorker.WorkDone \nEnd Sub<\/pre>\n
In the above code, the work_WorkDone <\/i>method will be called each time the WorkDone <\/i>event is raised. The Handles <\/i>clause after the method signature links the event-handling code with the actual event. <\/p>\n
A method can also dynamically link to an event using the AddHandler <\/i>method and be removed from handling an event using the RemoveHandler<\/i> method as seen below. This enables more flexibility by relating a method to an event and removing the binding required at runtime. Even when the Handles <\/i>keyword is used to bind a method to an event internally, a call to the AddHandler <\/i>method is done to perform the actual binding.<\/p>\n
‘We dont require to use WithEvents since we are binding to events dynamically 
Private mWorker As New Worker <\/p>\n
'Binds a method(handler) to an event \nAddHandler mWorker.WorkDone, AddressOf work_WorkDone \n'Unbinds a method(handler) from an event \nRemoveHandler mWorker.WorkDone, AddressOf work_WorkDone \n<\/pre>\n
Delegates in .NET events<\/h2>\n
VB.NET implements events through a construct called delegates. Delegates point to a method and can hold the address of a method, enabling a method to be invoked through an instance of its delegate. The Worker <\/i>class can be implemented without events using a delegate as follows:<\/p>\n
 Public Class Worker \n \n    Public Delegate Sub WorkDone(ByVal completedWork As Integer ) \n    Public Handler As WorkDone \n    Public Sub DoWork()  \n      For completedWork As Integer = 1 To 10 \n \n        System.Threading.Thread.Sleep(1000) \n        If handler IsNot Nothing Then\n          handler(completedWork * 10) \n        End If \n        Console.WriteLine(completedWork) \n \n      Next  \n    End Sub  \n  End Class <\/pre>\n
In the code above, a delegate named WorkDone <\/i>that accepts an integer argument has been defined. This delegate can point to any method with a similar signature (a sub-procedure that accepts an integer). After the delegate is defined, a public variable delegate named Handler <\/i>has been defined, and instead of raising the event in the DoWork<\/i> method, the delegate instance is invoked. <\/p>\n
In the Worker <\/i>class client, the delegate instance is set to point to the method that will be called when reporting the amount of work done.<\/p>\n
Private mWorker As new Worker \n'Sets the delegate instance to the method implementation \nmWorker.Handler = AddressOf work_WorkDone <\/pre>\n
The above code uses delegates directly, not the event construct, so neither the AddHandler<\/i> nor RemoveHandler<\/i> methods can be used. This exposes only one public variable, so there can be only one method to handle the invocation of the delegate. <\/p>\n
Directly using the delegates method eliminates the setting of multiple event handlers for one event source, which would notify all handlers when the event occurs. But an event type can be set as a delegate and use the event-handling mechanism, resulting in cleaner code as follows:<\/p>\n
  Public Class Worker \n \n    Public Delegate Sub WorkDone(ByVal completedWork As Integer ) \n    Public Handler As WorkDone \n    Public Sub DoWork()  \n      For completedWork As Integer = 1 To 10 \n \n        System.Threading.Thread.Sleep(1000) \n        RaiseEvent WorkEvent(completedWork * 10) \n        Console.WriteLine(completedWork) \n \n      Next  \n    End Sub  \n  End Class <\/pre>\n
Custom events in VB.NET 8.0<\/h2>\n
Custom events provide flexibility and control in creating and managing events. When using custom events, it is the responsibility of the developer to bind and unbind handlers, as well as to specify the actual calls to raise the events. Although this requires a bit more code than the earlier implementations, it provides more control over the handlers and the invocation.<\/p>\n
A custom event is defined by using the Custom keyword in front of the event declaration, and by providing the delegate type for the event. The custom event has three sections: The AddHandler<\/i> section, which is invoked whenever a handler is added using the Handles keyword or the AddHandler<\/i> method; RemoveHandler<\/i> section, which is called whenever a handler is removed using the RemoveHandler <\/i>method; and the RaiseEvent <\/i>section that will be invoked whenever an event is requested. The developer should write the necessary code in each of these sections to manage the handlers, as well as specify how handlers will be notified when an event is requested.<\/p>\n
Below, the Worker class is implemented using the custom event construct in VB.NET 2005. <\/p>\n
  Public Class Worker \n \n    Public Delegate Sub WorkDone(ByVal completedWork As Integer ) \n    Private handlers As New ArrayList() \n Public Custom Event WorkCompleted As WorkDone \n \n      AddHandler (ByVal value As WorkDone)\n \n        If handlers.Count <= 5 Then \n \n          handlers.Add(value)  \n        End If  \n      End AddHandler \n      RemoveHandler(ByVal value As WorkDone) \n        handlers.Remove(value)  \n      End RemoveHandler \n      RaiseEvent (ByVal completedWork >As Integer) \n \n        If completedWork > 50 Then  \n          For Each handler As WorkDone In handlers  \n            handler.Invoke(completedWork)  \n          Next  \n        End If  \n      End RaiseEvent  \n    End Event \n\n\n\n Public Sub DoWork() \n \n      For completedWork As Integer = 1 To 10  \n        System.Threading.Thread.Sleep(1000) \n        RaiseEvent WorkCompleted(completedWork * 10) \n        Console.WriteLine(completedWork) \n \n      Next  \n    End Sub  \n  End Class <\/pre>\n
Using custom events enables more control over the handlers. In the above code, for example, there is a condition in the AddHandler section limiting the number of handlers for which events are provided. The RaiseEvent method has been changed to notify the handlers only when the completed Work is more than 50. Another advantage to using custom events is a central unit of code containing all of the handlers of the event within the event construct.<\/p>\n
Using RaiseEvent twice, once in the DoWork method and then in the custom event construct, can lead to confusion. RaiseEvent in the DoWork method will raise the event, but the RaiseEvent section in the custom event construct specifies the code to be executed when the event is raised. In this case, all of the handlers are looped through and delegates are invoked.<\/p>\n
Events and delegates are important parts of the .NET language. VB.NET 2005 gives developers control and flexibility in handling simple event models and custom events.<\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"
Visual Basic .NET is well known for its event-driven programming capabilities. VB.NET 2005 adds new functionality for custom events that provides flexibility in handling and controlling events.…<\/p>\n","protected":false},"author":124595,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[143538],"tags":[4143,4229,4178,4330,4331,4179,4270,4194],"coauthors":[],"class_list":["post-107","post","type-post","status-publish","format-standard","hentry","category-dotnet-development","tag-net","tag-net-framework","tag-bi","tag-custom","tag-events","tag-source-control","tag-vb-net","tag-visual-basic"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/posts\/107","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/users\/124595"}],"replies":[{"embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/comments?post=107"}],"version-history":[{"count":5,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/posts\/107\/revisions"}],"predecessor-version":[{"id":42702,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/posts\/107\/revisions\/42702"}],"wp:attachment":[{"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/media?parent=107"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/categories?post=107"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/tags?post=107"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/coauthors?post=107"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}