This print for content only-size & color not accurate 7" X 9-1/4" / casebound / malloy

■

Source Code

The GenericDelegate project is located under the Chapter 11 directory.

That wraps up our initial look at the .NET delegate type. We will revisit some additional details

of working with delegates at the conclusion of this chapter and once again in Chapter 18 during

our examination of multithreading. Until then, let’s move on to the related topic of the C# event

keyword.

Understanding C# Events

Delegates are fairly interesting constructs in that they enable objects in memory to engage in a two-

way conversation. As you may agree, however, working with delegates in the raw can entail some

boilerplate code (defining the delegate, declaring necessary member variables, and creating custom

registration/unregistration methods to preserve encapsulation, etc.).

Typing time aside, another issue with using delegates in the raw as your application’s callback

mechanism is the fact that 

if you do not define a class’s delegate member variables as private, the

caller will have direct access to the delegate objects. If this were the case, the caller would be able to

reassign the variable to a new delegate object (effectively deleting the current list of functions to

call) and worse yet, the caller would be able to directly invoke the delegate’s invocation list. To

illustrate this problem, consider the following reworking (and simplification) of the previous

CarDelegate example:

public class Car

{