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:28 pm, "Simon Goldschmidt" <[email protected]> wrote: > Jb Evain wrote: > > Why would you need them in a merger? > > 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 will probably work without that, > as I have to walk all types and methods and adjust there references, > anyway... Does that prevent the need to iterate over the references per > module? If so, why did the old merger do it? > > Simon > -- > GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! > Jetzt freischalten unterhttp://portal.gmx.net/de/go/maxdome01 -- -- mono-cecil
