Solved

#import msxml3.dll + msxml.idl

Posted on 2002-03-15
5
898 Views
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?

Regards
-craig.
0
Comment
Question by:cmain
  • 3
  • 2
5 Comments
 
LVL 49

Expert Comment

by:DanRollins
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.
0
 
LVL 1

Author Comment

by:cmain
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!

Regards
-craig.
0
 
LVL 49

Expert Comment

by:DanRollins
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:

   http://www.experts-exchange.com/mfc/Q.20277317.html

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

Here is a link to a google thread

http://groups.google.com/groups?hl=en&ie=ISO-8859-1&oe=ISO-8859-1&threadm=eXSw7n90AHA.1576%40tkmsftngp03&rnum=7&prev=/groups%3Fq%3DIDL%2Band%2Bnamespace%2Band%2Bxml%26btnG%3DGoogle%2BSearch%26hl%3Den%26ie%3DISO-8859-1%26oe%3DISO-8859-1

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.

http://groups.google.com/groups?hl=en&ie=ISO-8859-1&oe=ISO-8859-1&threadm=250901c07cd0%243e6879d0%2434862ecf%40cpmsftngxa05&rnum=46&prev=/groups%3Fq%3DIDL%2Band%2Bnamespace%2Band%2Bxml%26hl%3Den%26ie%3DISO-8859-1%26oe%3DISO-8859-1%26start%3D40%26sa%3DN

Good luck.

-- Dan


0
 
LVL 1

Author Comment

by:cmain
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++.

Regards
-craig.
0
 
LVL 49

Accepted Solution

by:
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
0

Featured Post

How to improve team productivity

Quip adds documents, spreadsheets, and tasklists to your Slack experience
- Elevate ideas to Quip docs
- Share Quip docs in Slack
- Get notified of changes to your docs
- Available on iOS/Android/Desktop/Web
- Online/Offline

Join & Write a Comment

This is to be the first in a series of articles demonstrating the development of a complete windows based application using the MFC classes.  I’ll try to keep each article focused on one (or a couple) of the tasks that one may meet.   Introductio…
Exception Handling is in the core of any application that is able to dignify its name. In this article, I'll guide you through the process of writing a DRY (Don't Repeat Yourself) Exception Handling mechanism, using Aspect Oriented Programming.
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.
This video explains how to create simple products associated to Magento configurable product and offers fast way of their generation with Store Manager for Magento tool.

760 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

Need Help in Real-Time?

Connect with top rated Experts

23 Experts available now in Live!

Get 1:1 Help Now