Well seems like you're all set :) When you create a new TypeDefinition, the best thing to do is to immediately add it to a Module, this way it gets attached directly.
On Mon, Jan 20, 2014 at 2:31 PM, karl patrik johansson <[email protected]> wrote: > Without any further due, I was finally able to resolve this issue. It seem > like you get these kind of issues when you set a DeclaringType on a > TypeReference, pointing to a TypeDefinition, just leaving the default value > as it is worked. > > I previously set the DeclaringType because Mono.Cecil threw me an exception > on AssemblyDefinition.Write, as long as i'm setting a scope for the > TypeReference it will go smoothly. Which I didnt know when I first started. > > -- > -- > -- > mono-cecil > --- > You received this message because you are subscribed to the Google Groups > "mono-cecil" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. -- -- -- mono-cecil --- You received this message because you are subscribed to the Google Groups "mono-cecil" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
