Hello Jens, If you are removing a FieldDefinition from a TypeDefinition, then yes, you'll need to make all access to the removed FieldDefinition are replaced by the new FieldDefinition.
Jb On Wed, Mar 8, 2017 at 8:54 AM, Jens Christian Restemeier < [email protected]> wrote: > I was wondering, if I delete a field in as class and then add a new field > with the same name and type, do I need to update references in the rest of > the assembly? Or a better question, are internal references in the module > by name or by object? > > Basically I need to replace a class in an assembly with a class from a > different assembly. The interface is the same, only the implementation is > different. Unfortunately I can't use a runtime mechanism to achieve this, > and I need to actually change the DLL. And I have little experience with > .net and IL... > A quick and dirty solution should work, but so far searching on the > Internet I found more people with similar problems than solutions. I had it > almost working at one point through a roundtrip with IL assembly, but it > looks like the mono disassembler fails with some classes in the DLL. > > -- > -- > -- > 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/d/optout. > -- -- -- 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/d/optout.
