Re: distributing a COM library/server for use by other folks for C++

From:

"Alexander Nickolov" <agnickolov@mvps.org>

Newsgroups:

microsoft.public.vc.atl

Date:

Thu, 29 Jun 2006 11:39:52 -0700

Message-ID:

<uOTqpt6mGHA.1204@TK2MSFTNGP03.phx.gbl>

That would be ok for Automation-compatible interfaces.
Consider distributing the IDL as well. And you don't need
the _i.c file - it can be generated from the IDL if needed,
and with #import you are have the named_guids modifier.

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

"Jason S" <jmsachs@gmail.com> wrote in message
news:1151587232.372100.168520@b68g2000cwa.googlegroups.com...

If I have my compiled COM library/server (.dll for the purposes of this
discussion; could also be an .exe), what other file(s) are the best way
to distribute this for use by other people in their C++ clients? (Many
of us here are using MSVC 6.0, not sure if the answer is different for
more recent MSVC versions)

As far as I can tell, I can take just the .dll and the _i.c file
produced by MIDL, when I build the server. Then I can #import the .dll
and #include the _i.c file (for CLSIDs, somehow I can't seem to use
just the .dll file) & everything seems to work dandy.

Or I can #import the .tlb file instead of the .dll; this gives me the
ability to decouple the location of the dll's for installation, from
the .tlb / _i.c files needed for compilation.