Free mag vol1 | Page 578

CHAPTER 14  BUILDING AND CONFIGURING CLASS LIBRARIES

When you save your changes, the GUI editor updates your project’s AssemblyInfo.cs file, which is
maintained by Visual Studio and can be viewed by expanding the Properties node of the Solution
Explorer (see Figure 14-6).

Figure 14-6. The AssemblyInfo.cs file is updated as you use the GUI Properties editor
If you view the contents of this C# file, you’ll see a number of .NET attributes sandwiched between
square brackets. For example:
[assembly:
[assembly:
[assembly:
[assembly:
[assembly:
[assembly:
[assembly:
[assembly:

AssemblyTitle("CarLibrary")]
AssemblyDescription("")]
AssemblyConfiguration("")]
AssemblyCompany("")]
AssemblyProduct("CarLibrary")]
AssemblyCopyright("Copyright © 2012")]
AssemblyTrademark("")]
AssemblyCulture("")]

Chapter 15 examines the role of attributes in depth, so don’t sweat the details at this point. For now,
just be aware that a majority of the attributes in AssemblyInfo.cs will be used to update the .custom
token values within an assembly manifest.

Exploring the CIL
Recall that an assembly does not contain platform-specific instructions; rather, it contains platformagnostic common intermediate language (CIL) instructions. When the .NET runtime loads an assembly

520