Discussion:
MSXML topics missing from Index in Jan 2005 MSDN Library
(too old to reply)
Logos Bible Software
2004-12-21 21:33:22 UTC
Permalink
I understand that this might not be the most appropriate newsgroup for this
topic, but I couldn't find anywhere better in the list of MSDN managed
newsgroups.

Starting with the October 2004 MSDN Library, the MSXML topics have been
missing index entries. This makes it impossible to find them through the
"Index" tab of the MSDN Library viewer or through context-sensitive help.

To reproduce/demonstrate:

Install both the July 2004 and January 2005 MSDN Library DVDs.

Open July 2004 MSDN. Go to the Index tab and enter IXMLDOMNode. One of the
topics for that keyword should be:
ms-help://MS.MSDNQTR.2004JUL.1033/xmlsdk/htm/xml_obj_ixmldomnode_5xwl.htm

Right-click in the topic display and choose View > Source. Note the
following two lines in the HTML:
<MSHelp:Keyword Index="K" Term="IXMLDOMNode"/>
<MSHelp:Keyword Index="K" Term="IXMLDOMNode [MS XML], about IXMLDOMNode"/>
These cause an entry for "IXMLDOMNode" to be added to the MSDN Library Index
tab.


Open January 2005 MSDN. Go to the Index tab and enter IXMLDOMNode. The MSXML
topic is not listed under any of the (many) variations of this topic in the
Index. If you locate the page manually through the table of contents, you
will find that its URL is:
ms-help://MS.MSDNQTR.2005JAN.1033/xmlsdk/html/xmobjXMLDOMNode.htm

Right-click in the topic display and choose View > Source. There are no
lines that mention Index="K", hence the article has no entries in the Index
tab.

This problem makes the MSXML documentation almost impossible to use, because
it can't be found with a simple lookup in the index.

Thanks,
Bradley
Gary Chang[MSFT]
2004-12-22 09:24:47 UTC
Permalink
Hi, Bradley
Post by Logos Bible Software
This problem makes the MSXML documentation almost impossible to use, because
it can't be found with a simple lookup in the index.
It appears a problem in the new MSDN doc . Currently I will pass your
concern to the correspnding product team, and meantime I think you also can
post this issue to the MS wish site so as to suggest our dev guys to
improve
them in the furture MSDN doc:
http://register.microsoft.com/mswish/suggestion.asp


Thanks for your feedback and understanding!

Best regards,

Gary Chang
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
Logos Bible Software
2004-12-22 16:59:07 UTC
Permalink
Post by Gary Chang[MSFT]
It appears a problem in the new MSDN doc . Currently I will pass your
concern to the correspnding product team
Thanks!
Post by Gary Chang[MSFT]
, and meantime I think you also can
post this issue to the MS wish site so as to suggest our dev guys to
http://register.microsoft.com/mswish/suggestion.asp
I already found that site and posted feedback there (a few minutes after
sending the newsgroup post).

Thanks,
Bradley
Brad Mahugh [MS]
2005-02-04 23:21:02 UTC
Permalink
Bradley (and other MSXML SDK users):

I am lead writer for MSXML SDK. Your post was unfortunately the first I
found out we had a serious loss (misplacement actually) of index data when
converting to a new internal publishing system. The problem was quickly
remedied within a a couple days last week when I was forwarded your post by
another working in my team. We have since fixed our MSXML SDK doc build
process and we expect the corrected version to appear in the April 05 update
to MSDN.

I am truly sorry for this inconvenience and appreciate you bringing this to
our attention.

Best regards,
Brad Mahugh
Microsoft Corporation
Post by Logos Bible Software
Post by Gary Chang[MSFT]
It appears a problem in the new MSDN doc . Currently I will pass your
concern to the correspnding product team
Thanks!
Post by Gary Chang[MSFT]
, and meantime I think you also can
post this issue to the MS wish site so as to suggest our dev guys to
http://register.microsoft.com/mswish/suggestion.asp
I already found that site and posted feedback there (a few minutes after
sending the newsgroup post).
Thanks,
Bradley
Loading...