Sure enough, that seems to do the trick. Thanks! We've been, erm, hacking at this mostly successfully, but I don't think we would've ever figured this out without someone pointing us to it. Google never showed people deriving generic types from generic types, which is specifically the problem we had.
Yeah, I've also found out these things the hard way. And neither the docs nor the Reflection.Emit error messages help much in that learning process. Still, I'd advise to always check on MS Connect when you get strange behavior, there are quite a few bugs reported there concerning generics and Reflection.Emit. Sometimes, it really _is_ a weird platform bug. Especially avoid ldtokens on generic method and type definitions, if you can :) Fabian =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com