Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


XML conflict

From: cemil_azizoglu@-----.---
To: NULL
Date: 4/2/2006 10:56:00 PM

After adding code to my application to create publishing points, I
started receiving the following build error

c:\MSPSDK\Include\wmsxmldomextensions.h(726) : error C2872:
'IXMLDOMDocument' : ambiguous symbol
        could be 'c:\MSPSDK\Include\MsXml.h(1846) : IXMLDOMDocument'
        or       'c:\projects\GMX\Debug\msxml3.tlh(2098) :
MSXML2::IXMLDOMDocument'

My application uses SAX2 for parsing XML files to get initial
configuration parameters. I used the following headers as explained in
the platform SDK doc:

#import <msxml3.dll> raw_interfaces_only
using namespace MSXML2;

Everything used to work fine until the addition of code to create
windows media publishing points which must  #include "wmsserver.h".

It, in turn, includes MSXML.h which defines some of the same interfaces
such as IXMLDOMDocument defined in the type library msxml3.dll.

I'm aware of the following PRB:
"Compiler Errors When You Use #import with XML in Visual C++ .NET"
which suggests to qualify identifiers with MSXML2:: . My own code is
using namespace MSXML2 for parsing XML already. But the source of the
ambiguity comes from a windows media SDK header. I hope that I'm not
expected to go in and put qualifiers for wmsserver.h definitions, too.
There must be an easier way....

It's been several days and I can't get past this issue. Any help is
appreciated.

How do I resolve this ambiguity?

Thanks in advance,
Camako



transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent