Hey Simon, On Fri, Oct 28, 2011 at 12:41 AM, Simon <[email protected]> wrote: > that was the answer I was afraid of. It is sooo much easier to get a fix for > cecil than it is to get a fix for some part of visual studio. > Could this be the same issue? > http://code.google.com/p/notifypropertyweaver/issues/detail?id=94
Hmmm, again it's hard to tell. If this is related to the pdb, maybe FxCop/Phoenix tries to pick it in a different location. Once thing you can do, is to change the Mvid of the module to a new random guid. It will be written in the new pdb, and if FxCop loads another one, I'd expect it to either throw or bail out. Jb -- -- mono-cecil
