Currently there are some flaws to be aware of. First the install process does not take into account that many of us would just like to update the documentation we got with the WDK with the new docs. In fact, the installer does not even know about the WDK installation, and provides no way to update the documentation. I find that the installation of the WDK’s and its documentation are the least friendly parts of the product. After several attempts to install the updates, I finally pulled the doc files out of the underlying CAB file and put them in the help directory of the WDK where they belong.
The second problem is that the documentation does not have a feedback link so you can send in bug reports. This will be corrected in the next version, but for now the feedback alias is firstname.lastname@example.org. Having a well documented feedback alias is significant. Those who have been in the industry awhile may remember that when OSR hosted the documentation bug finding contest, the quality of the documentation went up significantly.
With all the new material in the documentation, there are errors. Now that there is a mechanism for providing feedback, and with frequent updates, we have a chance to fix these problems. Let’s roll up our sleeves and get to it. I am going to cut this entry short so I can send some mail about the technical mistakes I know of in the doc set.