I'd like to have property getters and methods that I can decorate with my own custom attribute and based on the presence of that attribute replace the method bodies with a different implementation. Also, that different implementation will need to know the constructor arguments given to the custom attribute where it decorates the method.
This can obviously be done with AOP, like PostSharp or LinFu, but I'm wondering if there's a way to do this that does not involve a post-build processing step because adding that complicates the project more than I would prefer.
There exists a couple of frameworks that allows you to dynamically change any method at runtime:
There are some possibilities, depending on your exact needs. Ever since .NET 1.0, it has been possible to intercept calls using the the types in the System.Runtime.Remoting.Proxies namespace.
Using the traditional .Net APIs there is no way to achieve this. Method bodies are fixed at compile time and cannot be changed.
I say traditional though because with the profiler and ENC APIs it's technically possible to change method bodies. But these APIs operate in constrained circumstances and are not considered to be general purpose APIs.
It is possible with any good AOP framework working at runtime. I currently work on one of them with this capacity.
You can find it here : NConcern .NET runtime Aspect-Oriented Programming
A little example to show you how it work...
The supposed custom attribute :
Example of a marked classe :
Use case :