Search:

For differences between the various versions of VS2019, see https://www.tektutorialshub.com/visual-studio/difference-between-visual-studio-2019-community-vs-professional-vs-enterprise/

Have you tried creating a completly new solution with just the existing source files? IMO there's a solution file used in debugging that contains a wrong file reference. Try doing a file search for...

Just for interest/info - we stopped creating .dll's several years ago. We also stopped splitting classes into header/implementation files. Everything is now in .hpp files that are included as needed...

PS Has this fixed the previous error with the debug build with the missing subfolder? [ https://forums.codeguru.com/showthread.php?565257-Strange-crash-with-Debug-build ]

Under SDK's, libraries and frameworks - I have:

C++ ATL for latest v142 build tools (x86 & x64)
Windows 10 SDK (10.0.19041.0)

Yeah - Several C++ questions asked in this forum should be asked in the C++ (Non-visual C++ Issues) forum.

If both were built with VS2019, then I don't know. Other than there seems to be something wrong with your VS install. I'd be tempted to completely remove it and re-install from scratch. Have you got...

Yes - for OLE automation. There's quite a few different types - BSTR possibly being the most well known. They are not part of C++ though. These were developed by MS to help with interoperability with...

yes - probably because of different versions of std::stringstream exe/dll. You can't mix versions! This is the sort of thing that was called 'dll hell'! In the above, std::stringstream default...

All sins forgiven :)

I suspect that the class definition for stringstream used in the .dll is different from that used in the .exe. That's probably why it compiles OK with VS2008, but not VS2019. There has been large...

In C++, true is 1 and false is 0. This can be shown by:



bool z = true;

printf("%02x\n", (unsigned char)z);


which displays 01 as expected.

You can't mix 32 bit and 64 bit libraries/exe. They must all be compiled as either 32 bit or 64 bit. See https://docs.microsoft.com/en-us/windows/win32/winprog64/process-interoperability

After the find, you don't check if site hasn't been found.



auto it = std::find(m_TacToUnassignedNeighSiteKeysList[tac].begin(), m_TacToUnassignedNeighSiteKeysList[tac].end(), site);...

If these containers have many elements, consider the performance impacts of all of these 'by value' copies being done.

1) Usually const auto& rather than auto so that you pass by ref and not by value.

2) If neighkeys is auto& (by ref) and neighkeys is passed by ref to ApplyinitialDistanceHOCriterion(), won't that...

Also https://stackoverflow.com/questions/28411283/dealing-with-attribute-in-msvc

What's an example of the external symbol that can't be found - and what is called in the .dll?

We all have those 'senior moments'........ :)

Are you compiling as C or C++? If as C++, are the function declarations for the dll functions specified as extern "C" (capital C) to avoid name 'mangling'? See...

Is this the same as your post here https://forums.codeguru.com/showthread.php?565160-_local_stdio_printf_options

Just generate the .lib file from the .dll. See https://stackoverflow.com/questions/9946322/how-to-generate-an-import-library-lib-file-from-a-dll See the .bat file(s) that automate this process.

You can't. C++20 compatibility is only available with VS2019.

I don't use boost!

struct MyStruct {
int (*foo)();
};

static int func1()
{
printf("I am called\n");
return 0;
}