Thanks on the tip.
I was reading about dynamic assemblies and found some information on
peverify. It helped me track down an issue I was having and thus getting it
resolved.
Dynamic assemblies are very nice indeed.
Thanks,
Mike
On Fri, Jul 18, 2008 at 2:26 AM, Fabian Schmied <[EMAIL PROTECTED]>
Don't forget to run your generated assemblies through peverify - just
because Reflector can load them doesn't mean they are actually
valid/verifyable (and thus safe to use).
Fabian
===
This list is hosted by DevelopMentor® http://www.develop.com
View archives and
Thanks Peter.
The example you have is pretty much what I have figured out.
I spend a lot of trial and terror to figure out some of this stuff.
Part of the problem was that I was not seeing any reflected code in
Reflector. I figured out that I needed to set the emitSymbolInfo parameter
on the Asse
If you provide example code we can probably point out what's missing/needs-
correction. I don't know off hand how you can write a valid assembly to
disk without being able to read types with Reflector/ILDASM.
Here's the most simple case of dynamnically creating an assembly:
AssemblyName assembly
I'm needing to do some dynamic code generation.
I've been reading up on the Reflection.Emit namespace but I'm having some
issues.
When I compile a dynamic assembly and then save to disk, I can't read the
types from it in Reflector or ILDASM.
Do any of you have any good tutorials or sample code I m
