For reference:
https://jacobfilipp.com/msj-index/
And also MSDN.
For reference:
https://jacobfilipp.com/msj-index/
And also MSDN.
Part of the reason they did so well, companies could easily implement software using the new APIs.
Of course, they also had secret and undocumented APIs that people found and wanted to use ...
If you just wanted to do c++ windows programming you can get visual studio which, I believe, did come with Win32 documentation (especially as CD roms became common distro methods).
The c++ software development kit itself (just libraries, documentation, and samples, no tooling) wasn't too expensive and was mainly material costs.
https://download.microsoft.com/download/1/6/d/16d24ada-5317-...
5,000+ pages...I think this is the FULL documentation for everything related to VB 2005.
My preference was for a mid-tier subscription that provided a complete set of licensed-for-development-use Windows Server, and Microsoft Office and SQL Server ISOs, for ~$495/year.
Of course, you had no way of knowing that the truly eye-watering top-tier $2000/yr MSDN subscriptions were jam-packed with junky "Enterprise" tools that you would never actually want or need, without actually purchasing one. Nor would you know that the priority support credits bundled with top-tier MSDN support did not materially improve upon the "shouting into the void" nature of unpaid support, which in turn was not materially better than the No Support At All for U option that we currently have. Although my one experience with a paid priority support case did actually produce an actual fix three years later. So there is that, I suppose. :-/