Is it possible to run some code when an assembly is loaded, without doing anything specific in the loading code? What I am looking for is like a static constructor on a type
You should probably revisit your serialization approach to mitigate this problem. If you serialize using ISerializable
and the SerializableAttribute
attribute, you can make it such that the serialization graph will load assembly B when necessary without assembly A ever having to explicitly know about assembly B.
There are 3 options to initialize a .NET Assembly:
You can use static constructors in .Net, but unfortunately they don't do what you want. Static constructors are only executed just before a type is used. See http://msdn.microsoft.com/en-us/library/k9x6w0hc(VS.80).aspx for details.
You might get some mileage from subscribing to your AppDomain's AssemblyLoad event. See http://msdn.microsoft.com/en-us/library/system.appdomain.assemblyload.aspx.
In your event handler you could reflect on the newly loaded assembly, and get it to execute whatever code you like.
Using a mixed assembly you can get DllMain to run on an assembly load.
(edit - applies to C#; for a C++ approach, see this answer)
Basically, no: you can't. This would be a huge attack surface, and isn't allowed. You might want to put a static ctor on some of the B types that ensure the init code is executed, but that is about it...
The CLR supports module initializers. You'd have to hack C++/CLI code or ilasm.exe to use them.