Ordering Advices

The article Coping with Several Aspects on the Same Target describes aspect dependencies and aspect ordering. Most of it also applies to advices. When we talk about the order of execution of aspects, we mean the order of execution of advices. Aspects themselves are never executed.

Dependencies defined at aspect level implicitly apply to all advices. When developing a member-level aspect or a type-level aspect with advices (see Developing Member-Level Aspects and Developing Type- and Assembly-Level Aspects), you can add dependencies directly to advice methods by annotating them with custom attributes of the namespace PostSharp.Aspects.Dependencies.

Note that all advices provided by an aspect are ordered in a single block. Suppose that a method is the target of advices Aspect1.MethodA, Aspect1.MethodB and Aspect2.MethodC. The next table shows valid and invalid orders:

Ordering advices of the same aspect

Advices of the same aspect can be ordered using any custom attribute derived from AspectDependencyAttribute.

Because advices of the same aspect instance are necessarily ordered as a block, it is appropriate to specify dependencies between aspect classes extensively, and specify ordering of advices only in the scope of the current aspect instance. The most appropriate dependency custom attribute for this purpose is AdviceDependencyAttribute, which accepts the name of the advice method as a parameter.

See Also

Reference

AdviceDependencyAttribute