G
Guest
Hello,
I've created a regular (as opposed to extension) DLL that has MFC support
(in a shared DLL). Everything works fine. I then decided to modify my
configuration so that on the project level I turned on CLR support. Now,
when I try to rebuild my solution I get linker errors
fileName.obj : error LNK2028: unresolved token (0A000ACF) "void __stdcall
_com_issue_error(long)" (?_com_issue_error@@$$FYGXJ@Z) referenced in function
"void __cdecl _com_util::CheckError(long)" (?CheckError@_com_util@@$$FYAXJ@Z)
fileName.obj : error LNK2019: unresolved external symbol "void __stdcall
_com_issue_error(long)" (?_com_issue_error@@$$FYGXJ@Z) referenced in function
"void __cdecl _com_util::CheckError(long)" (?CheckError@_com_util@@$$FYAXJ@Z)
Is having MFC in the DLL plus CLR support at the project level something
that should work? If so, anything you can suggest to help resolve my
compilation problem?
Thanks,
Notre
I've created a regular (as opposed to extension) DLL that has MFC support
(in a shared DLL). Everything works fine. I then decided to modify my
configuration so that on the project level I turned on CLR support. Now,
when I try to rebuild my solution I get linker errors
fileName.obj : error LNK2028: unresolved token (0A000ACF) "void __stdcall
_com_issue_error(long)" (?_com_issue_error@@$$FYGXJ@Z) referenced in function
"void __cdecl _com_util::CheckError(long)" (?CheckError@_com_util@@$$FYAXJ@Z)
fileName.obj : error LNK2019: unresolved external symbol "void __stdcall
_com_issue_error(long)" (?_com_issue_error@@$$FYGXJ@Z) referenced in function
"void __cdecl _com_util::CheckError(long)" (?CheckError@_com_util@@$$FYAXJ@Z)
Is having MFC in the DLL plus CLR support at the project level something
that should work? If so, anything you can suggest to help resolve my
compilation problem?
Thanks,
Notre