Metalama VS Fody

Metalama allows you to create your own code validation rules without the complexity of Roslyn. It is especially useful to validate source code against architecture or design patterns.

Metalama allows you to create your own code validation rules without the complexity of Roslyn. It is especially useful to validate source code against architecture or design patterns.

Metalama allows you to create your own validation rules without the intricacies of Roslyn analyzers. This can be useful to implement architecture-as-code, i.e. validate the source code against architectural or pattern guidelines.

Metalama allows you to create your own validation rules without the intricacies of Roslyn analyzers. This can be useful to implement architecture-as-code, i.e. validate the source code against architectural or pattern guidelines.

Metalama is a comprehensive aspect-oriented framework for C#.

While NConcern aims to remain a lightweight AOP implementation, Metalama is a comprehensive meta-programming framework that includes a full aspect-oriented framework, code analysis and code generation. It is based on Roslyn and integrates with source generators.

Metalama is a comprehensive aspect-oriented framework based on Roslyn written by the creators of PostSharp. It integrates with source generators, analyzers, diagnostic suppressors, and code fix providers.

While Fody works at binary (MSIL) level, Metalama Compiler is a fork of Roslyn and allows for AST transformations, at the C# level.

As an alternative to PostSharp you may take a look at Fody.

Working with IL weaving as part of the building process is quite complex though, and this is where Fody enters into the picture. Fody is an extensible tool that allows to simplify the weaving process by taking care of all the heavy lifting.

Fodyplugins can modify exists code during compilation.

I've seen coworkers using Fody for such MSIL weaving stuff, but I have a bad feeling about this. It's a little bit like jailbreaking your phone. Cool stuff ahead, but voids warranty.

Implement your own (in C++/outside dotnet/CLR) IHostAssemblyManager stuff, this is the "replace/bypass how assemblies are loaded" trick. There used to be a prebuilt thing on the old old codepages, but I can't find it. I wonder if newer code/assemblie weavers such as Fody can do the similar thing?

Great place to start is https://github.com/Fody/Fody and existing 'addins' - fody does it at compile time - generally quite useful for your own code if you want to dip into aspect oriented programming.