#import msxml3.dll + msxml.idl

Posted on 2002-03-15
Last Modified: 2013-11-20
I would like to import msxml3.dll using a #import because that way I get the smart pointers.

This requires the use of the MSXML2 namespace. I cannot leave out the namespace with
using namespace MSXML2 because the symbols conflict and become ambiguous.

I also wish to use IXMLDOMDocument pointers in my idl file, but idl does not recognise namespaces.

There is a conflict here that I cannot resolve.
If you know how to use the #import and reference the imported symbols in an idl please let me know.
This is a common problem to which there seems to be no solution?

Question by:cmain
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
LVL 49

Expert Comment

ID: 6869612
In the IDL file, can't you just use a generic IDispatch pointer?  Just make sure the clients are aware that it is an MSXML3::IXMLDOMDocument .  I think that is stndard operating procedure.

-- Dan

P.S.  That namespace stuff caused me endless grief when I first started using IXMLDOMDocument.

Author Comment

ID: 6876408
Yes, I could do that.
It works reasonably well using IUnknown pointers. The problem is that my customers want strongly typed interfaces; and I cannot, in all good consience, disagree with them!

LVL 49

Expert Comment

ID: 6878207
Worth a try:  Post a 0-pt question with a title like:
   IDL and namespace
and in the question put a link to this Q:

Post it in the XML TA and C++ TA.  Some of those experts distain MFC...

Here is a link to a google thread

In the final post, the guy seems to know what he is talking about.

Perusing some related thereads, it seesm that there is some agreement that problem is that Microsoft seriously goofed in how they set up MSXML.  We wouldn't need to use namespaces at all if they had planned ahead.

At least one person thinks that it is simply impossible to pass an IXMLDomDocument accross a COM interface.

In the final post in this thread, the user says that s similar post was fixed by installiung the latesd Platform SDK.

Good luck.

-- Dan


Author Comment

ID: 6879129
Hi Dan,

I think that the one person who thinks it cannot be done is correct. They have seriously screwed up on the namespaces. The midl compiler should be able to ascertain that IXMLDOMDocument is isomorphic to MSXML2::IXMLDOMDocument and it cannot.

I have searched quite a bit. The only way to actually get it vaguely correct is to use 'using namespace MSXML2' in stdafx.h. The problem with this is that you need to spend hours hacking out the standard headers because they include the older xml declarations.

M$ don't do a whole lot correctly when it comes to c++.

LVL 49

Accepted Solution

DanRollins earned 300 total points
ID: 6879226
Yes, I agree that the problem is that the standard header files assume/require the old definitions.  And for no apparent reason, the XMLDOM headers seem to be brought in  for completely unrelated classes.

>>M$ don't do a whole lot correctly when it comes to c++.

I have to disagree with that.  The next best programming IDE is a distant second place in terms of getting actual programming done.  Microsoft VC++ is often a target just because there are 10 programmers who use it for every one person who uses something else.  Now 10 people are likely to find (and yell about) a bug a lot sooner (and louder) than one person :)  

-- Dan

Featured Post

On Demand Webinar - Networking for the Cloud Era

This webinar discusses:
-Common barriers companies experience when moving to the cloud
-How SD-WAN changes the way we look at networks
-Best practices customers should employ moving forward with cloud migration
-What happens behind the scenes of SteelConnect’s one-click button

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Turn a spreadsheet into a vba executable. 2 103
Separate into files by filename 12 92
Expand macro to ask for filename column 8 40
sum67 challenge 35 130
Introduction: Displaying information on the statusbar.   Continuing from the third article about sudoku.   Open the project in visual studio. Status bar – let’s display the timestamp there.  We need to get the timestamp from the document s…
Introduction: Hints for the grid button.  Nested classes, templated collections.  Squash that darned bug! Continuing from the sixth article about sudoku.   Open the project in visual studio. First we will finish with the SUD_SETVALUE messa…
This video will show you how to get GIT to work in Eclipse.   It will walk you through how to install the EGit plugin in eclipse and how to checkout an existing repository.

752 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question