J
jlea
I'm getting the following link error in my C++/.NET C++ project:
error LNK2022: metadata operation failed (8013118D) : Inconsistent layout
information in duplicated types (tagTOOLINFOA): (0x020000af).
I've done some internet research and have follewed the suggested procedure
of using ildasm and have confirmed that the type "tagTOOLINFOA" is in fact
at 0x020000af, but unfortunately I don't know what to do at this point. I
have messed around with stdafx.h with no luck and have changed compiler
settings for the offending class, again with no luck.
If someone knows what the trick is to fix this lovely little error I'd
really appreciate it. If someone from MS could enlighten the rest of us or
if somene from MS who knows what this means or could ask the linker guys
what this error message is trying to tell us (other than meta data is
inconsistent), again, I'd really appreciate it.
We are following MS's advice of compiling only those files necessary with
/clr so the project is a mixture of /clr and non-/clr code so maybe that is
causing the problem. We have numerous other mixed projects like the current
one and we don't have any problems.
Jon.
error LNK2022: metadata operation failed (8013118D) : Inconsistent layout
information in duplicated types (tagTOOLINFOA): (0x020000af).
I've done some internet research and have follewed the suggested procedure
of using ildasm and have confirmed that the type "tagTOOLINFOA" is in fact
at 0x020000af, but unfortunately I don't know what to do at this point. I
have messed around with stdafx.h with no luck and have changed compiler
settings for the offending class, again with no luck.
If someone knows what the trick is to fix this lovely little error I'd
really appreciate it. If someone from MS could enlighten the rest of us or
if somene from MS who knows what this means or could ask the linker guys
what this error message is trying to tell us (other than meta data is
inconsistent), again, I'd really appreciate it.
We are following MS's advice of compiling only those files necessary with
/clr so the project is a mixture of /clr and non-/clr code so maybe that is
causing the problem. We have numerous other mixed projects like the current
one and we don't have any problems.
Jon.