Fody VS NTypewriter

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.

I am currently using NTypewriter for code generation.

With NTypewriter you can generate anything. It connects Scriban templates with data exposed from Roslyn API. You can run templates from VS (design time) or embed them (run time) into your application with the help of Buildalayzer.

With NTypewriter you can generate clients for any language (TS, Java), because you have full control over generated code, but similar to other tools, it uses C# as an input language.

You can use NTypewriter for that, it is mainly for generating typed TS clients, but in general, you can generate whatever you want.

You can try to use NTypewriter for code generation, but its main purpose is generation of java script clients for APIs or documentation.

NTypewriter is better and alive, but I am definitely biased.