Jb! I have a question. Questions about copying methods/types from one type or assembly to another is a main problem in the framework. So may be it can be resolved by using _one_ reference to one type from different assemblies. For example, I copy some type from one place to another. If this type uses types from public library (user library or GAC library), Cecil must just add reference to this public library, not deep copy with a lot of resolvings and imports. Its a very big minus to do deep copying. Developers cannot solve theirs tasks, they solves problem to copy methods bodies.
On 30 мар, 14:42, "Simon Goldschmidt" <[email protected]> wrote: > Simon Cropp <[email protected]> wrote: > > Simon > > > Do you think you could split that code out and push it to Cecil.Rocks? > > I'd love to do that. However, the code has some special cases for type > references that are copied, which are kind of special for a merger. Also, > il-repack is still work-in-progress in some points and I guess putting code > in cecil.rocks is up to Jb, as he would have to maintain it, then. OTOH, that > would be a good thing to do since it would always be up-to-date when cecil > changes... > > Simon > -- > GMX DSL Doppel-Flat ab 19,99 Euro/mtl.! Jetzt mit > gratis Handy-Flat!http://portal.gmx.net/de/go/dsl -- -- mono-cecil
