So is it considered a bug for DefaultAssemblyResolver to resolve 2 different instances for the same type/method?
An isolated case that I find it consistently happens is when you resolve from .net reflection Type system. For instance, when you call myClassDef.Module.Resolve(typeof(MyClass)). It will always return a different typedefinition instance (from what you already have loaded within the module). I'm not in a position to send you a sample repo right now, will try to make one later, but I hope the case I described suffices for now. Cheers On Fri, Aug 19, 2011 at 3:29 PM, Jb Evain <[email protected]> wrote: > Hi, > > On Fri, Aug 19, 2011 at 1:37 AM, Hendry Luk <[email protected]> wrote: > > Mono-cecil tends to return different > > typedefinition/methoddefinition/instructiondefinitions instances for the > > same code structure. This holds true even when I use > > DefaultAssemblyResolver. > > Please provide a self contained repro which demonstrates that, so it > can be fixed. > > Thanks! > > Jb > > -- > -- > mono-cecil -- -- mono-cecil
