On Thu, Aug 4, 2011 at 5:00 PM, Timwi <[email protected]> wrote: > Why not? Sorry if this is a dumb question, but I was able to find the > property or field by name from the type definition and retrieve its > type from there.
Then it only works for fields and properties defined in the current module. Cecil tries hard to not load another module unless it explicitly has too. And that's the case here, we have a perfectly valid representation, a bit cumbersome for boxed values admittedly, but workable. Jb -- -- mono-cecil
