[RESOLVED] Compiling Simconnect 3.4.x with Visual Studio 2017

[seippg]

I'm getting several linker errors attempting to build a project using the Simconnect 3.4.x libraries. I could compile without a problem the older (much older) libraries. Is there a workaround or a way to get updated libraries?

Thanks,
Gregg

To be clear, these are the errors the linker is throwing...

1>SimConnect.lib(commClient.obj) : error LNK2038: mismatch detected for '_MSC_VER': value '1800' doesn't match value '1900' in Calculator.obj
1>SimConnect.lib(commClient.obj) : error LNK2038: mismatch detected for '_ITERATOR_DEBUG_LEVEL': value '0' doesn't match value '2' in Calculator.obj
1>SimConnect.lib(commClient.obj) : error LNK2038: mismatch detected for 'RuntimeLibrary': value 'MD_DynamicRelease' doesn't match value 'MDd_DynamicDebug' in Calculator.obj
1>LINK : warning LNK4098: defaultlib 'MSVCRT' conflicts with use of other libs; use /NODEFAULTLIB:library
1>SimConnect.lib(SimConnectClient.obj) : error LNK2019: unresolved external symbol "__declspec(dllimport) char const * __cdecl std::_Winerror_map(int)" (__imp_?_Winerror_map@std@@YAPBDH@Z) referenced in function "public: virtual class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > __thiscall std::_System_error_category::message(int)const " (?message@_System_error_category@std@@UBE?AV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@2@H@Z)
1>SimConnect.lib(commClient.obj) : error LNK2019: unresolved external symbol __imp___vsnprintf referenced in function "long __cdecl StringCbPrintfA(char *,unsigned int,char const *,...)" (?StringCbPrintfA@@YAJPADIPBDZZ)
1>SimConnect.lib(client.obj) : error LNK2019: unresolved external symbol __imp__printf referenced in function "public: virtual void __thiscall CClient::Reset(void)" (?Reset@CClient@@UAEXXZ)

[WarpD]

I believe you will have to use older VisualC libraries to get this to compile.

[seippg]

I believe you will have to use older VisualC libraries to get this to compile.

2015 work or do I need to go back to 2013?

[WarpD]

For v3 I believe they used Visual Studio 2013.

[seippg]

For v3 I believe they used Visual Studio 2013.

Thanks, I'll see if it works.

[seippg]

For v3 I believe they used Visual Studio 2013.

Thanks, I'll see if it works.

Downgraded to VS2013 and, yes, it did compile. Thanks for your help.