PostSharp.Extensibility Namespace

No equivalent in Metalama.

No equivalent in Metalama.

No equivalent in Metalama.

No equivalent in Metalama.

To escalate Metalama warnings into errors, use the same strategy as for C# or analyzer errors.

No equivalent in Metalama.

There is no equivalent in Metalama. This logic is currently hard-coded.

No equivalent in Metalama.

In Metalama, a message is represented by a IDiagnostic. To instantiate a diagnostic, you must first declare its DiagnosticDefinition<T> as a static field or property, then use WithArguments(T).

In Metalama, messages are called diagnostics and they must be defined as static fields of aspects or fabrics using the DiagnosticDefinition<T> class.

No equivalent in Metalama.

In Metalama, the equivalent is IDiagnosticLocation.

No equivalent in Metalama.

No equivalent in Metalama.

Okay, this one is problematic. There is no declarative (attribute-based) multicasting in Metalama. Instead, fabrics should be used. However, we have ported the main features of MulticastAttribute to Metalama. See MulticastAspect or MulticastImplementation.

See the remarks on MulticastAttribute.

There is no full equivalent of this attribute in Metalama, and there will not be. To mark an aspect as inherited, use the InheritableAttribute custom attribute. To specify the eligibility of an aspect, implement the BuildEligibility(IEligibilityBuilder<T>) method.

In Metalama, use the custom attribute to enable aspect inheritance. By default, Metalama implements the Strict inheritance mode. If you need multicasting, see MulticastAspect or MulticastImplementation.

In Metalama, the valid targets are determined by the declaration types for which the IAspect<T> interface is implemented. Additionally, you can implement the BuildEligibility(IEligibilityBuilder<T>) method. However, the main features of MulticastAttribute have been ported to Metalama. The equivalent to this attribute is MulticastTargets.

In Metalama, use MetalamaExecutionContext.

In Metalama, use ProjectExtension. However, all project extensions are programmatic. Metalama does not support XML configuration.

In Metalama, use RequireAspectWeaverAttribute.

There is no equivalent in Metalama.

In Metalama, use the same mechanism as for suppressing C# or analyzer warnings.

No equivalent in Metalama.

In Metalama, use MetalamaExecutionContext.Current.FormatProvider.

In Metalama, messages are called diagnostics and they must be defined as static fields of aspects or fabrics using the DiagnosticDefinition<T> class.

In Metalama, an IDeclaration is also a IDiagnosticLocation.

In Metalama, the equivalent is Metalama.Framework.Diagnostics.IDiagnosticSink.

In Metalama, use MetalamaExecutionContext.

In Metalama, use IProject.

No equivalent in Metalama.

In Metalama, use IService.

In Metalama, use IServiceProvider.

No equivalent in Metalama.

In Metalama, use IAspect<T> and implement BuildEligibility(IEligibilityBuilder<T>) and/or BuildAspect(IAspectBuilder<T>).

No equivalent in Metalama.