Re: Interface Methods Nof Found During Link

From:

"Alexander Nickolov" <agnickolov@mvps.org>

Newsgroups:

microsoft.public.vc.atl

Date:

Tue, 2 Jan 2007 15:05:05 -0800

Message-ID:

<uX4XxJsLHHA.3668@TK2MSFTNGP02.phx.gbl>

Make sure you either compile and link the _i.c file or
#include it in exactly one source file. I'm assuming you
are not using any framewrok for COM, otherwise this
would have already been done for you...

--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@mvps.org
MVP VC FAQ: http://vcfaq.mvps.org
=====================================

"Ken Wilson" <kwilson.dev@NsOhSaPw.cAaM> wrote in message
news:9bjlp2hr5082lk3vgvfjngah6jankro44e@4ax.com...

I am new to COM and, unfortunately, studying from a somewhat dated
text. For the most part I have been able to reason my way around
challenges but have run into a dead end currently. I am working on
sample code intended to produce an inproc dll. The sample code
compiles but fails during linking with the following two errors;

LNK2001: unresolved external symbol _IID_IQuotation Fortune3.obj
LNK2001: unresolved external symbol _IID_IFortuneTeller Fortune3.obj

I'm on a Win2K machine using Visual Studio 2005 with unmanaged C++. I
suspect the problem is with the C++ name mangling but don't know how
to circumvent it. The COM methodology is still Greek enough for me
that suddenly being fed a bunch of MFC macros to accomplish things
appears only to confuse the situation.

Any insight into things I could be checking out are greatly
appreciated. Also, I'd rather not get into the religious war of MFC
vs. ATL as this is academic exploration on my part at this time. I am
just trying to increase my understanding of the COM paradigm.

Thanks in advance.

--
Ken Wilson
Looking for viable employment in Victoria, BC