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

// Assign description using a "named property."

[Serializable]

[VehicleDescription(Description = "My rocking Harley")]

public class Motorcycle

{

}

[SerializableAttribute]

[ObsoleteAttribute("Use another vehicle!")]

[VehicleDescription("The old gray mare, she ain't what she used to be...")]

public class HorseAndBuggy

{

}

[VehicleDescription("A very long, slow, but feature-rich auto")]

public class Winnebago

{

}

C H A P T E R   1 6  

■

T Y P E   R E F L E C T I O N, L AT E   B I N D I N G, A N D  AT T R I B U T E - B A S E D   P R O G R A M M I N G

547

8849CH16.qxd  10/9/07  4:27 PM  Page 547

---

Named Property Syntax

Notice that the description of the Motorcycle is assigned a description using a new bit of attribute-

centric syntax termed a 

named property. In the constructor of the first [VehicleDescription]

attribute, you set the underlying System.String using a name/value pair. If this attribute is reflected

upon by an external agent, the value is fed into the Description property (named property syntax is

legal only if the attribute supplies a writable .NET property).

In contrast, the HorseAndBuggy and Winnebago types are not making use of named property syn-

tax and are simply passing the string data via the custom constructor. In any case, once you compile

the AttributedCarLibrary assembly, you can make use of ildasm.exe to view the injected metadata

descriptions for your type. For example, Figure 16-8 shows an embedded description of the

Winnebago type.

Figure 16-8.

Embedded vehicle description data