As you saw in Chapter 2, you can use attributes to alter the outcome of the compilation process. But that is not the only time attributes come into play. Some attributes are examined as the code is running, and their presence in the assembly results in certain actions. For example, security-based attributes can be used to state that certain permissions must exist; otherwise, the code will not execute. Other attributes allow an object’s state to be persisted to disk. This chapter will cover some of these runtime attributes and how they affect your code as it executes. We’ll start our investigation of runtime attributes by looking at .NET security.
KeywordsCustomer Class Runtime Behavior Static Void Employee Structure Remote Object
Unable to display preview. Download preview PDF.