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

[mscorlib]System.Delegate::Combine(

class [mscorlib]System.Delegate, class [mscorlib]System.Delegate)

castclass CarEvents.Car/CarEventHandler

stfld class CarEvents.Car/CarEventHandler CarEvents.Car::AboutToBlow

ret

}

As you would expect, remove_AboutToBlow() will indirectly call Delegate.Remove() and is more

or less identical to the previous RemoveAboutToBlow() helper method:

.method public hidebysig specialname instance void

remove_AboutToBlow(class CarEvents.Car/CarEventHandler 'value')

cil managed synchronized

{

.maxstack  8

ldarg.0

ldarg.0

ldfld class CarEvents.Car/CarEventHandler CarEvents.Car::AboutToBlow

ldarg.1

call class [mscorlib]System.Delegate

[mscorlib]System.Delegate::Remove(

class [mscorlib]System.Delegate, class [mscorlib]System.Delegate)

castclass CarEvents.Car/CarEventHandler

stfld class CarEvents.Car/CarEventHandler CarEvents.Car::AboutToBlow

ret

}

Finally, the CIL code representing the event itself makes use of the .addon and .removeon direc-

tives to map the names of the correct add_XXX() and remove_XXX() methods to invoke:

.event CarEvents.Car/EngineHandler AboutToBlow

{

.addon void CarEvents.Car::add_AboutToBlow

(class CarEvents.Car/CarEngineHandler)

.removeon void CarEvents.Car::remove_AboutToBlow

(class CarEvents.Car/CarEngineHandler)

}

Now that you understand how to build a class that can send C# events (and are aware that

events are little more than a typing time-saver), the next big question is how to “listen to” the

incoming events on the caller’s side.