I have always wanted to know about Microsoft's Platform SDK design process in terms of how they go from a set of related API's designed and implemented in the OS as a set of DLL's to the final MSDN API Help Pages that are written and exposed to the public for consumption as part of the Platform SDK.

Questions that come to mind:
1) Are the devs that implement the API's code the same devs that design them and document them

2) Who writes all the MSDN API LIbrary Help; is it the same devs that implement the API

3) Is the MSDN API Help text written in the same source code files and then stripped using automated tools to generate the Docs?

4) Is there a difference between all the .H file in the Platform SDK that we get compared to what the OS and API source code .c/.cpp files use to compile the OS DLL's that contain the implementation.

  - How do you go about structuring the pool of source files so that they can be seperated for internal (Private to MSFT) vs external (Platform SDK) use.

I have never been able to find good material or books to help with the design process of producing and seperating a PUBLIC Software Development Kit (SDK) from the PRIVATE section of the code that is used to compile the platform that the SDK is intende to target.

Heston