As explained in the section Understanding Aspect Lifetime and Scope , a different aspect instance is associated with every element of code it is applied to. Aspect instances are created at compile time, serialized into the assembly as a managed resource, and deserialized at run time. If the aspect is instance-scoped, instances are duplicated from the prototype and initialized.
Therefore, you can override one of the following three methods to handle aspect initializations:
CompileTimeInitializeis invoked at compile time, and should initialize only serializable fields of the aspect, so that the value of these fields will be available at run time. The argument of this method is the System.Reflection object representing the element of code to which this aspect instance has been applied. Therefore, this method can already perform expensive computations that depend only on metadata.
RuntimeInitializeis invoked at run time. Note that the aspect constructor itself is not invoked at run time. Therefore, overriding
RuntimeInitializeis the only way to perform initialization tasks at run time. If the aspect is instance-scoped, this method is executed on the prototype instance.
The methods CreateInstance(AdviceArgs) and RuntimeInitializeInstance() is invoked only for instance-scoped aspects. They initialize the aspect instance itself, as
RuntimeInitializewas invoked on the prototype.
Initializing an aspect at compile time is useful when you need to compute a difficult result that depends only on metadata -- that is, it does not depend on any runtime information. An example is to build the strings that need to be printed by a tracing aspect. It is rather expensive to build strings that contain the full type name, the method name, and eventually placeholders for generic parameters and parameters. However, all required pieces of information are available at compile time. So compile time is the best moment to compute these strings.