Comments on: Module initializers in C#

By: einar

einar — Tue, 10 Jan 2012 09:01:52 +0000

@Aura: Actually, as I was looking through the source now to update it, I saw that the WriterParameters and ReaderParameters that are sent into WriteAssembly and ReadAssembly have a .SymbolStream property. You might be able to give them a stream to your .pdf files directly there, if you’re willing to hack on it a bit.

By: einar

einar — Tue, 10 Jan 2012 08:51:30 +0000

@newl: Great. I actually just went and fixed those issues in the source. The latest source is up at github, at http://github.com/einaregilsson/InjectModuleInitializer. I’ll make an update to the blog post soon and release a new merged assembly as well.

By: newl

newl — Tue, 10 Jan 2012 00:37:59 +0000

Thanks for the response einar.

Changing that in the InjectInitializer method and also removing the TypeReference in the FullName call of GetCalleeMethod and replacing the value passed into the Equals method to “System.Void” seems to have resolved the culture issue when targeting framework 4.

Now to try and figure out why the dependent assembly that I have embedded in a dll isn’t being loaded using this new method.

By: einar

einar — Mon, 09 Jan 2012 15:01:18 +0000

@newl: I haven’t tested this but you could try changing this line in InjectInitializer:

TypeReference voidRef = Assembly.MainModule.Import(typeof(void));

TypeReference voidRef = callee.ReturnType;

That *should* work, since you’re getting a void reference from the targeted assembly, but I haven’t tried to compile this or anything. Let me know how it works out

By: newl

newl — Mon, 09 Jan 2012 06:02:28 +0000

I’m receiving the same culture related exception that was mentioned above. I too am targeting .NET Framework v4 assembly.

Juan mentioned that he was able to fix it and doesn’t appear to have provided a patch. Simply retargeting the solution for framework 4 doesn’t resolve the issue. What is the fix?

By: einar

einar — Sat, 07 Jan 2012 18:35:31 +0000

@Aura: Sorry, no, I have no idea how exactly it gets the pdb name. I browsed quickly throught the Cecil source at https://github.com/jbevain/cecil/tree/master/Mono.Cecil but it’s hard to figure out

By: Aura

Aura — Thu, 05 Jan 2012 20:59:48 +0000

This is exactly what I’m looking for and I’d be happy even if you can’t answer what I’m asking, but…

It seems like it tries to look for the pdb file in the same directory as the assembly that I’m trying to inject. Is there a way for me to specify where the pdb file is, using Mono.Cecil.Pdb, when calling ReadAssembly() and WriteAssembly() in the class InjectModuleInitializerImpl? Documentation seems to be not abundant for Mono.Cecil to say the least.

By: Simon Cropp

Simon Cropp — Wed, 10 Aug 2011 23:01:53 +0000

Einar

Just a short thanks because this post helped me build this

http://code.google.com/p/costura/wiki/HowItWorksEmbedTask

Keep up the good work.

By: einar

einar — Wed, 13 Jul 2011 08:36:05 +0000

@Juan: Cool. Are you on Github by any chance? I haven’t updated the blog post, but the code lives on github at https://github.com/einaregilsson/InjectModuleInitializer . If you’re there, please fork, patch, and send me a pull request!

By: Juan Campa

Juan Campa — Wed, 13 Jul 2011 06:18:33 +0000

Ok, I can now confirm that the double referencing *was* the problem. It didn’t worked the first time because the void type was being imported while crafting the injected method also. I changed this so that the void TypeReference is taken out of the target assembly instead of the currently excecuting CLR. It’s now working fine.

Thanks once again,
Juan