topic Re: Linker errors in .NET Forum

Linker errors

Anonymous — Fri, 27 Jan 2017 18:56:23 GMT

I brought a project in to VS 2017 from VS 2013 and now I get a ton of linker errors.

Severity	Code	Description	Project	File	Line	Suppression State
Error	LNK2028	unresolved token (0A00061B) "public: wchar_t const * __cdecl AcString::kwszPtr(void)const " (?kwszPtr@AcString@@$$FQEBAPEB_WXZ) referenced in function "public: __cdecl AcString::operator wchar_t const *(void)const " (??BAcString@@$$FQEBAPEB_WXZ)	....	

Severity	Code	Description	Project	File	Line	Suppression State
Error	LNK2028	unresolved token (0A000613) "public: class AcRxObject * __cdecl AcRxClass::create(void)" (?create@AcRxClass@@$$FQEAAPEAVAcRxObject@@XZ) referenced in function "private: class Detailer::Common::TPG_Material * __clrcall Detailer::Common::TPG_MaterialMgd::GetInternalObject(void)" (?GetInternalObject@TPG_MaterialMgd@Common@Detailer@@$$FAE$AAMPEAVTPG_Material@23@XZ)	Detailer.dotNET.Entities

I have been over all of my library includes and cannot for the life of me find which is missing. The following files are added to the "Additional Dependencies" list:

rxapi.lib
acdb21.lib
acge21.lib
acdbmgd.lib

As you can see one is related to AcString and the other is related to AcRxObject. I have upgraded the project settings to point to the new ObjectArx 2017 directory for the include and lib files. This builds in 2013 no problem.

Any hints?

Mike

Re: Linker errors

Alexander.Rivilis — Fri, 27 Jan 2017 21:48:12 GMT

>>>I brought a project in to VS 2017 from VS 2013 and now I get a ton of linker errors.<<<
VS 2017???

Re: Linker errors

Alexander.Rivilis — Fri, 27 Jan 2017 23:49:40 GMT

You have to include also ac1st21.lib

Re: Linker errors

Anonymous — Sat, 28 Jan 2017 16:09:35 GMT

VS 2017 Release candidate. Everything is good though. I removed most of my includes and project .lib declarations from project settings in favour of #include "arxHeaders.h".

Re: Linker errors

Alexander.Rivilis — Sat, 28 Jan 2017 16:43:37 GMT

@Anonymous wrote:
VS 2017 Release candidate.

IMHO. It's a good idea not to use the recommended version of Visual Studio (2015). Especially one that has not Release yet.