>From a previous discussion so it ends up on the list. Cecil may have some issues in sustained running situations as keeping a single TypeDef can hold on to a lot of objects. The obvious answer is to build your own model on top of cecil and project into your own model though this is very time consuming (and is basically just duplication).
JB mentioned using module.Types.Remove(TypeDef) to detach a given typedefinition. Another option would be to copy into a detached version. I imagine that one Types.Remove(TypeDef) is called, you just won't be able to walk through the module anymore which is ok. For the copying does anyone happen to have a copy around? What about MethodDefs? How would they be detached? Greg -- Les erreurs de grammaire et de syntaxe ont été incluses pour m'assurer de votre attention -- -- mono-cecil
