Re: Implementing an interface
You misunderstood my post. You don't need to use any of the
stuff generated by #import - it's completely redundant. I only
gave you a workaround for the missing LIBID to use a namespace
with #import. Everything else but the LIBID in that namespace
you don't need to use. When you figure out the right LIBID
symbol to use, you can remove the #import again.
--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@mvps.org
MVP VC FAQ: http://vcfaq.mvps.org
=====================================
<Mike.Spertus@veritas.com> wrote in message
news:812d5978-249c-4cc8-8809-b1056d2484b6@5g2000hsg.googlegroups.com...
If I get rid of the no_namespace, what else needs to be done? At the
least, I will have to add namespaces to the signature of many of the
methods that were generated by the "Implement Interface" command. I
can do that, but will there be lots of other generated code that will
be broken by using a namespace (e.g., will the generated IDispatch
still work, etc.)? If I have to start editing files with big "DO NOT
EDIT" warnings on top, what is the impact?
Mike
On Jan 3, 12:56 pm, "Alexander Nickolov" <agnicko...@mvps.org> wrote:
I'm not excactly familiar with MS XML. I'm sure there's another
symbol defined in MS headers you are supposed to use, so you
may want to ask in an MS XML-centric group. As a workaround you
can reinstate the #import and remove no_namespace from the
attribute list - replace it with rename_namespace(your_choice) and
then use your_choice::LIBID_MSXML2 instead.
--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnicko...@mvps.org
MVP VC FAQ:http://vcfaq.mvps.org
=====================================
<Mike.Sper...@veritas.com> wrote in message
news:f98378fe-cc18-4f3e-bfc6-24f6891e6af6@s8g2000prg.googlegroups.com...
Thanks for the suggestion Alexander. If I remove it, a lot of errors
go away but I get
Error 1 error C2065: 'LIBID_MSXML2' : undeclared identifier
This occurs in the following line (in the superclass list generated
for my class).
public IDispatchImpl<IXMLDOMNode, &__uuidof(IXMLDOMNode),
&LIBID_MSXML2, /* wMajor = */ 4>
What else do I need to do?
On Jan 3, 12:08 pm, "Alexander Nickolov" <agnicko...@mvps.org> wrote:
Remove the #import generated by the wizard - you don't need it.
The wizard is designed for third party type libraries thus you need
to clean up after it.
--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnicko...@mvps.org
MVP VC FAQ:http://vcfaq.mvps.org
=====================================
<Mike.Sper...@veritas.com> wrote in message
news:0c81b21d-acb9-403d-91b7-68bab69a81f7@t1g2000pra.googlegroups.com...
On Jan 2, 6:08 pm, Mike.Sper...@veritas.com wrote:
I am trying to implement the IXMLDOMNode interface (so that MSXML
can
manipulate some of my custom objects). I create a simple COM object
using the ATL Simple object wizard. I then choose "Implement
Interface" and select IXMLDOMNode. However, it doesn't even compile
at
this stage (even though I've just used the wizard and not written
any
of my own code). When stdafx.cpp is compiled, I get tons of errors
like the followng.
Error 3 error C2011: 'IXMLDOMImplementation' : 'struct'
type
redefinition
c:\bld_area\client\src\webcontentbho\atlwrappeddom\debug
\msxml4.tlh 331
Looking a little more closely, I see that it is complaining that
this
types are defined both in "msxml.h" (which it is somehow including)
and in msxml4.tlh. How can I get rid of these errors?
Thanks,
Mike
I've looked at this a little more, and the problem appears to be
that
the Wizard generated code imports MSXML4.dll with the no_namespace
option, which collides with the MSXML used elsewhere with COM. This
is
somewhat related tohttp://support.microsoft.com/kb/316317/EN-US/,
which is about problems that arise whenever importing MSXML DLLs.
However, the KB doesn't address how to handle the problem when
Wizard
generated code imports MSXML.