The use case is as follows: I am writing a tool that takes a bunch of assemblies and changes the types and methods as per user-defined rules/conventions (say, all types derived from Form should be XXXForm). If the type/method changes in one assembly, the corresponding reference in other assemblies should change too.
--- Unless there is an alternate way to change the references, iterating over all of them and changing them would really need the TypeReferences and MemberReferences API. It would be really great if you can add that. Thanks John On Jul 28, 4:37 pm, Jb Evain <[email protected]> wrote: > On Wed, Jul 28, 2010 at 1:28 PM, Simon Goldschmidt <[email protected]> wrote: > > Hmm, the old merger iterates over them and drops duplicates (and adjusts > > them to the merged references, I think). I didn't yet get to the point > > where I can test whether that's really needed or not. > > It's not needed with 0.9, as it ensures there's no duplicate type ref > and member ref. > > -- > Jb Evain <[email protected]> -- -- mono-cecil
