Namespace PostSharp.Aspects

In PostSharp, this object exposed the run-time execution context to the advice. However, in Metalama, advice do not execute at run time. Instead, advice are templates that generate run-time code. This run-time code does not need helper objects to represent the execution context.

In Metalama, use meta.Target.Parameters.ToValueArray().

The base aspect class in Metalama is Aspect.

In Metalama, use DescriptionAttribute.

This class was unused in PostSharp and has no equivalent in Metalama.

In PostSharp, this class was used with IAspectProvider. In Metalama, no additional object is necessary when adding an aspect instance. Read-only access to aspect instances is provided through the IAspectInstance interface.

There is no equivalent to this class in Metalama.

There is no equivalent to this class in Metalama.

In Metalama, use CompilationAspect.

There is no composition aspect in Metalama, but you can build one by deriving the TypeAspect type, implementing the BuildAspect(IAspectBuilder<INamedType>) method, and calling builder.Advice.ImplementInterface(INamedType, INamedType, OverrideStrategy, object?). There is no concept of protected interface in Metalama.

There is no specific aspect class to add a custom attribute in Metalama, but only the advice factory method IntroduceAttribute(IDeclaration, IAttributeData, OverrideStrategy). Create an aspect class that calls this advice factory method from BuildAspect(IAspectBuilder<T>).

In PostSharp, this object exposed the run-time execution context to an event interception advice. However, in Metalama, advice do not execute at run time. Instead, advice are templates that generate run-time code. This run-time code does not need helper objects to represent the execution context.

In Metalama, use OverrideEventAspect. Overriding aspect invocation is not yet implemented in Metalama. There is currently no workaround.

In Metalama, use EventAspect.

In Metalama, use FieldOrPropertyAspect.

In Metalama, use TypeAspect. Note that aspects in Metalama have no run-time existence, so they cannot be instance-scoped. While porting a PostSharp InstanceLevelAspect into Metalama, you would typically introduce instance fields or properties into the target type, and use an initializer to initialize them.

This feature is not implemented in Metalama.

In PostSharp, this object exposed the run-time execution context to the advice. However, in Metalama, advice do not execute at run time. Instead, advice are templates that generate run-time code. This run-time code does not need helper objects to represent the execution context.

In PostSharp, this object exposed the run-time execution context to the advice. However, in Metalama, advice do not execute at run time. Instead, advice are templates that generate run-time code. This run-time code does not need helper objects to represent the execution context.

In Metalama, use OverrideFieldOrPropertyAspect.

In Metalama, use FieldOrPropertyAspect.

Not implemented in Metalama.

In PostSharp, this object exposed the run-time execution context to the advice. However, in Metalama, advice do not execute at run time. Instead, advice are templates that generate run-time code. This run-time code does not need helper objects to represent the execution context.

In Metalama, use OverrideMethodAspect.

In PostSharp, this object exposed the run-time execution context to the advice. However, in Metalama, advice do not execute at run time. Instead, advice are templates that generate run-time code. This run-time code does not need helper objects to represent the execution context.

Use OverrideMethodAspect.

Equivalent to IAspect<T> where T is IMethod.

Not supported in Metalama, but it is now supported by C# itself.

No equivalent in Metalama.

In Metalama, use OverrideMethodAspect and write your own try/catch block.

In Metalama, use OverrideMethodAspect.

There is no equivalent to this type in Metalama. The equivalent concept can be built manually.

No equivalent in Metalama. To override an async method, implement the OverrideMethodAspect.OverrideAsyncMethod() method and call meta.ProceedAsync().

No equivalent in Metalama. To override an async method, implement the OverrideMethodAspect.OverrideAsyncMethod() method and call meta.ProceedAsync().

No equivalent in Metalama. To override an async method, implement the OverrideMethodAspect.OverrideAsyncMethod() method and call meta.ProceedAsync().

No equivalent in Metalama. To override an async method, implement the OverrideMethodAspect.OverrideAsyncMethod() method and call meta.ProceedAsync().

The base aspect interface is IAspect.

Aspects are purely build-time in Metalama, so all semantics are build semantics. The equivalent interface is therefore IAspect.

Use IAspectInstance.

In Metalama, you can add aspects using fabrics. In aspects, implement the BuildAspect(IAspectBuilder<T>). In fabrics, implement AmendType(ITypeAmender), AmendProject(IProjectAmender) or AmendNamespace(INamespaceAmender). In both cases, call the IAspectReceiverSelector<TTarget>.With<TMember>(System.Func<TTarget,System.Collections.Generic.IEnumerable<TMember>>) method, then call AddAspect<TAspect>().

In Metalama, use extension methods of the code model.

Equivalent to IAspect<T> where T is ICompilation.

Equivalent to IAspect<T> where T is ICompilation.

In PostSharp, a binding was a run-time object that allowed the run-time code of the aspect to call the target code. In Metalama, aspects no longer have run-time code. Instead, they have templates that are expanded at compile time and generate run-time code. Templates can generate run-time code that accesses target code using dynamic code or invokers. For methods, use meta.Target.Method.Invoke(params dynamic?[]).

In Metalama, use OverrideMethodAspect.

There is no built-in support for cloning in Metalama at the moment.

There is no composition aspect in Metalama, but you can build one by deriving the TypeAspect type, implementing the BuildAspect(IAspectBuilder<INamedType>) method, and calling builder.Advice.ImplementInterface(INamedType, INamedType, OverrideStrategy, object?). There is no concept of protected interface in Metalama.

There is no specific aspect class to add a custom attribute in Metalama, but only the advice factory method IntroduceAttribute. Create an aspect class that calls this advice factory method from BuildAspect(IAspectBuilder<T>).

In PostSharp, a binding was a run-time object that allowed the run-time code of the aspect to call the target code. In Metalama, aspects no longer have run-time code. Instead, they have templates that are expanded at compile time and generate run-time code. Templates can generate run-time code that accesses target code using dynamic code or invokers. For events, use meta.Target.Event.Add(dynamic?), Remove(dynamic?) or Raise(params dynamic?[])

Equivalent to IAspect<T> where T is IEvent.

Equivalent to IAspect<T> where T is IEvent.

Equivalent to IAspect<T> where T is IField.

Equivalent to IAspect<T> where T is IField.

Not supported in Metalama because aspects no longer have a run-time existence. Instead, they only exist at compile time, and generate run-time code.

No equivalent in Metalama.

In PostSharp, a binding was a run-time object that allowed the run-time code of the aspect to call the target code. In Metalama, aspects no longer have run-time code. Instead, they have templates that are expanded at compile time and generate run-time code. Templates can generate run-time code that accesses target code using dynamic code or invokers. For fields and properties, use meta.Target.FieldOrProperty.Value.

There is no equivalent in Metalama.

In PostSharp, a binding was a run-time object that allowed the run-time code of the aspect to call the target code. In Metalama, aspects no longer have run-time code. Instead, they have templates that are expanded at compile time and generate run-time code. Templates can generate run-time code that accesses target code using dynamic code or invokers. For fields and properties, use meta.Target.FieldOrProperty.Value.

In PostSharp, this interface exposed the run-time execution context to a location interception advice. However, in Metalama, advice do not execute at run time. Instead, advice are templates that generate run-time code. This run-time code does not need helper objects to represent the execution context.

There is no equivalent in Metalama.

In PostSharp, this interface exposed the run-time execution context to a location interception advice. However, in Metalama, advice do not execute at run time. Instead, advice are templates that generate run-time code. This run-time code does not need helper objects to represent the execution context.

In Metalama, use OverrideFieldOrPropertyAspect.

Equivalent to IAspect<T> where T is IFieldOrProperty.

Equivalent to IAspect<T> where T is IFieldOrProperty.

In Metalama, use ContractAspect.

In Metalama, use ContractAspect.

Not implemented in Metalama.

In PostSharp, a binding was a run-time object that allowed the run-time code of the aspect to call the target code. In Metalama, aspects no longer have run-time code. Instead, they have templates that are expanded at compile time and generate run-time code. Templates can generate run-time code that accesses target code using dynamic code or invokers. For methods, use meta.Target.Method.Invoke(params dynamic?[]).

In Metalama, use OverrideMethodAspect.

Equivalent to IAspect<T> where T is IMethod.

Equivalent to IAspect<T> where T is IMethod.

In Metalama, use OverrideMethodAspect and write your own try/catch block.

There is no equivalent of this aspect in Metalama because Metalama rewrites the code in such a way that field or property initializations go through the overridden setter. This is done by moving the initializers to the constructor, where it is safe to call the aspect.

Use OverrideMethodAspect and implement your own try/catch/finally block.

This feature is not implemented in Metalama and there is no workaround.

Equivalent to IAspect<T> where T is INamedType.

Equivalent to IAspect<T> where T is INamedType.

There is no equivalent in Metalama because OnMethodBoundaryAspect is implemented with OverrideMethodAspect as a method template, therefore you have full control on the control flow.

Equivalent to ContractDirection.

There is no equivalent in Metalama because Metalama will throw an exception if the target is not supported.