What is IL Weaving?

Question

I just saw Ayende's post today about PostSharp. I downloaded the code and tried it out, and I thought it was the coolest, most easy to use way to handle AOP that I've seen.

In his post, Ayende says that PostSharp accomplishes it's magic via IL Weaving. Now, at some abstract level I can deduce what that means, but I wanted to see if there was a more detailed answer out there. Unfortunately, for the first time in a very long time, Google came up empty for me. And so I thought this would be a great question for StackOverflow (since I've been a subscribe to Jeff's blog for a couple years now and knew this site was doing its thing).

So what exactly is IL Weaving and how is it accomplished?

Answer 1

IL Weaving is simlar to ByteCode Weaving. .Net compiles to an intermediate language which is run by the .NET clr. IL Weaving is basically analyzing the and altering the the intermediate language. Since it is done at that level it can be done for all .NET languages.

Answer 2

Might help if you Google MSIL Injection instead. This link is from PostSharp and it explains it well.

My company has recently bought a product called dynaTrace for performance diagnosis. It uses MSIL injection to instrument around methods. Basically it adds IL code before your method and after to time the method (I am sure there is a lot more to it than that).

And here is a fairly involved but good explanation of the process.

Answer 3

Weaving refers to the process of injecting functionality into an existing program. This can be done conceptually at a number of levels:

• Source code weaving would inject source code lines before the code is compiled
• IL weaving (for .NET) adds the code as IL instructions in the assembly
• ByteCode weaving (for Java) works on the class file, see these comments wrt AspectJ

In theory you could go one deeper and weave with an executable compiled to native instructions, but this would add a lot of complexity and I'm not aware of anything that does this.