The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
What annoys me really is that they did not get the redirection of MSDN pages to MS Docs work properly. If you have a MSDN link for a wide version of an API function, it redirects to the ANSI version at MS Docs!
As a result, all existing answers here at CP and elsewhere containing MSDN links to API functions will now open the ANSI version when clicked. Another side effect is when inserting MSDN links now here at CP, the ANSI title from the Docs page is inserted while the link itself is still to MSDN.
Well that is a different issue; I was talking about the answers posted to questions in some of the Microsoft forums. I have always found (with a few exceptions that are less important) the information on MSDN to be useful and well presented.
But when I built the program all the version related functions gave LNK2019 errors, unresolved external symbol.
Go back and #define WINVER and _WIN32_WINNT and recompile. The old version.lib is for legacy desktop applications. It sounds like you are either using an older compiler or targeting an older operating system < Windows 8.
It's basically a documentation issue. The documentation is incorrect if you are targeting older platforms. Much of the documentation will be moving to GitHub.
No, none of those, it's a linker problem, not compiler. The issue has nothing to do with versions of Visual Studio or Windows (I'm using VS2017 on Windows 10), it's purely the fact that the A versions of those functions are not in Mincore.lib, despite the statement in the documentation.
But this issue is purely about the C/C+ Windows libraries. And there are still many programs around that use ASCII. And judging by questions here, many new programmers are not being taught to use Unicode.