MS has been great with documentation, but sadly in the recent years they've also been "outsourcing" a lot of the work to GitHub and relying on "community" to fix everything they broke in the horrid MSDN->docs migration. I use their docs daily, and I regularly come across stuff like this:
I've also noticed a relatively huge amount of grammar/spelling errors in their newer docs, no doubt because MS has lost much of its real documentation team.
Fortunately most of my work with Win32 uses stable APIs that have been around since Win95/NT4, and thus are nicely documented in the infamous WIN32.HLP.
https://docs.microsoft.com/en-us/windows/win32/api/winsock/n...
Compare with the MSDN page which is surprisingly still there (if it isn't when you read this, check the Internet Archive):
https://msdn.microsoft.com/en-us/windows/ms741519(v=vs.100)
Or just plain misleading, like this function which definitely returns a value but has "void" in place of the actual type:
https://docs.microsoft.com/en-us/windows/win32/api/wininet/n...
The page on MSDN is correct as usual:
https://msdn.microsoft.com/en-us/windows/aa385098(v=vs.80)
I've also noticed a relatively huge amount of grammar/spelling errors in their newer docs, no doubt because MS has lost much of its real documentation team.
Fortunately most of my work with Win32 uses stable APIs that have been around since Win95/NT4, and thus are nicely documented in the infamous WIN32.HLP.