jasonbock/injectors

A code injection framework for .NET

Injectors

This project allows a developer to specify injectors that will run on an assembly to modify its contents. The code uses Cecil (http://www.mono-project.com/Cecil) to do the heavy lifting.

injectors's Issues

Auto-Implement Dispose Checker

If you implement IDisposable, you should throw ObjectDisposedException whenever any member on your object is used after Dispose() is called. Doing something like this:

[CheckForDispose]
public class MyClass : IDisposable { // ... }

Would do that check for the developer.

Add a Initialization Interface For Virtual Method Usage

See my blog post:

http://www.jasonbock.net/News/Item/e19c6d5f9bd5448296b16a7b16817b3c

Create a MaximumCall Attribute

This would be for methods, like this:

[MaximumCall(1)]
public void SomeMethod() { }

Code would be added to ensure the method was called only once.

This would be interesting as this could enforce a singleton:

[MaximumCall(1)]
public MyClass() { }

If you tried to create more than one MyClass, it would fail.

Create a CodeAnalysis SuppressMessage Attribute Remover

Simple: get rid of all these attributes in an assembly. They're only needed for CA; they don't need to stick around once the static analysis is complete.

Create an AutoLock Property for Methods

This is a wild, probably silly, idea, but it would be fun (more than anything) to pull of.

Basically, the idea is simple:

[Lock]
public void SomeMethod() { }

So if someone calls it, it would automatically add the "locK" semantics around this method call, whether it's static or instance.

Again, this is fraught with issues, but it would be fun to see how far I could push it.