|Important||This document may not represent best practices for current development, links to downloads and other resources may no longer be valid. Current recommended version can be found here. ArchiveDisclaimer|
Parameters and Return Values for Multithreaded Procedures
Supplying and returning values in a multithreaded application is complicated because the constructor for the thread class must be passed a reference to a procedure that takes no arguments and returns no value. The following sections show some simple ways to supply parameters and return values from procedures on separate threads.
The best way to supply parameters for a multithreaded method call is to wrap the target method in a class and define fields for that class that will serve as parameters for the new thread. The advantage of this approach is that you can create a new instance of the class, with its own parameters, every time you want to start a new thread. For example, suppose you have a function that calculates the area of a triangle, as in the following code:
You can write a class that wraps the CalcArea function and creates fields to store input parameters, as follows:
To use the AreaClass, you can create an AreaClass object, and set the Base and Height properties as shown in the following code:
Notice that the TestArea procedure does not check the value of the Area field after calling the CalcArea method. Because CalcArea runs on a separate thread, the Area field is not guaranteed to be set if you check it immediately after calling Thread.Start. The next section discusses a better way to return values from multithreaded procedures.
Returning values from procedures that run on separate threads is complicated by the fact that the procedures cannot be functions and cannot use ByRef arguments. The easiest way to return values is to use the BackgroundWorker component to manage your threads and raise an event when the task is done, and process the results with an event handler.
The following example returns a value by raising an event from a procedure running on a separate thread:
Private Class AreaClass2 Public Base As Double Public Height As Double Function CalcArea() As Double ' Calculate the area of a triangle. Return 0.5 * Base * Height End Function End Class Private WithEvents BackgroundWorker1 As New System.ComponentModel.BackgroundWorker Private Sub TestArea2() Dim AreaObject2 As New AreaClass2 AreaObject2.Base = 30 AreaObject2.Height = 40 ' Start the asynchronous operation. BackgroundWorker1.RunWorkerAsync(AreaObject2) End Sub ' This method runs on the background thread when it starts. Private Sub BackgroundWorker1_DoWork(ByVal sender As Object, _ ByVal e As System.ComponentModel.DoWorkEventArgs) _ Handles BackgroundWorker1.DoWork Dim AreaObject2 As AreaClass2 = CType(e.Argument, AreaClass2) ' Return the value through the Result property. e.Result = AreaObject2.CalcArea() End Sub ' This method runs on the main thread when the background thread finishes. Private Sub BackgroundWorker1_RunWorkerCompleted(ByVal sender As Object, _ ByVal e As System.ComponentModel.RunWorkerCompletedEventArgs) _ Handles BackgroundWorker1.RunWorkerCompleted ' Access the result through the Result property. Dim Area As Double = CDbl(e.Result) MsgBox("The area is: " & Area) End Sub
You can provide parameters and return values to thread-pool threads by using the optional ByVal state-object variable of the QueueUserWorkItem method. Thread-timer threads also support a state object for this purpose. For information on thread pooling and thread timers, see Thread Pooling and Thread Timers.