Can u upload a solution that illustrates the issue?
On 05/12/2010, at 10:41 AM, joer <[email protected]> wrote: > JB, > > I assumed so to, but unfortunately even after hours of debugging I am > lost where the error could be. > > So Assembly A has some classes Assembly B inherits. A verifies fine. > So what do I need to import into B from A ? If I step in my IL > Instructions, all types seem to resolve just fine. If the IL > references a field of Class in Assembly B where the field is declared > in the base class in class A, do I need to import such ? I thought I > can and must only import types and methods ? > > There is one hint in peverify output where it complains with an > unresolved token (instead of a bogus token) which is a public field of > the Base class in Assembly A called by a class in Assembly B. > > Do I have to import ALL types and methods of Assmebly A into Assembly > B although B already has a reference to A and uses types of a ? > > Joe > > > > On Dec 3, 6:34 pm, Jb Evain <[email protected]> wrote: >> Hi, >> >> On Sat, Dec 4, 2010 at 12:31 AM, joer <[email protected]> wrote: >>> I am trying to alter 2 assemblies at the same time. if I alter only >>> one, all is fine, but with both I only get chaos. While cecil shows >>> all correct during weaving , the resulting MSIL has invalid tokens all >>> over. >> >> There should not be any issue with modifying two modules in memory. My >> guess is that you're getting your imports wrong. >> >> Jb > > -- > -- > mono-cecil -- -- mono-cecil
