The IntelliSense feature does not work for the IXMLDOMDocumentPtr smart pointer

This article has been archived. It is offered "as is" and will no longer be updated.
When you use the IXMLDOMDocumentPtr smart pointer in the code that is generated when you import the Mmsxml4.dll file in your project in Microsoft Visual Studio .NET 2003, the IntelliSense feature for the smart pointer does not work.
The IntelliSense engine cannot correctly interpret the smart pointer definitions.
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Visual Studio .NET 2003 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date         Time   Version            Size    File name   --------------------------------------------------------------   16-Apr-2004  03:42  13.10.4107.0      933,888  C1.dll              16-Apr-2004  03:42  13.10.4107.0    2,207,744  C1xx.dll            16-Apr-2004  11:35  13.10.4107.0    1,966,080  Feacp.dll           16-Apr-2004  03:50                      5,342  Feacp.lib
To work around this problem, type the typedef for the smart pointer in your pointer declaration. Instead of declaring your smart pointer like this:
You can declare your pointer by using the typedef:
_com_ptr_t<_com_IIID<MSXML2::IXMLDOMDocument, 0x0> > pXMLDoc = NULL;
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
More information
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Article ID: 840873 - Last Review: 01/17/2015 09:40:32 - Revision: 3.0

Microsoft Visual Studio .NET 2003 Academic Edition, Microsoft Visual Studio .NET 2003 Enterprise Architect, Microsoft Visual Studio .NET 2003 Enterprise Developer

  • kbnosurvey kbarchive kbqfe kbhotfixserver KB840873