declaring coclasses. Have all your coclasses expose
the IUnknown interface instead in the type library. Right
default interfaces of coclasses. Having them as non-
I think I'm getting a little of track. Here's what I'd like to
accomplish:
Once my COM exe server is complete, I'd like VB clients to be able to
reference it by selecting the exe itself as a reference and create
objects
from it using the defined interfaces.
I have a type library built that looks like this:
[
uuid(<GUID>),
version(1.0),
helpstring("My 1.0 Type Library")
]
library MyLib
{
importlib("stdole2.tlb");
[
uuid(<GUID>),
helpstring("My Class")
]
// Forward reference all interfaces
interface IMyInterface1;
interface IMyInterface2;
interface IMyInterface3;
[
object,
uuid(<GUID>),
dual,
nonextensible,
helpstring("MyInterface1"),
pointer_default(unique)
]
interface IMyInterface1 : IDispatch {
[id(1), propget] HRESULT Id([out, retval] long* );
[id(2), propget] HRESULT Name([out, retval] BSTR* );
};
<Other interfaces here>
};
In my COM exe project's IDL file I import that type library:
[
uuid(<GUID>),
version(1.0),
helpstring("ServerTest 1.0 Type Library")
]
library ServerTestLib
{
importlib("stdole2.tlb");
importlib("MyLib.tlb"); // import type library!!
[
uuid(<GUID>),
helpstring("MyInterface1 Class")
]
coclass MyInterface1
{
[default] interface MyLib.IMyInterface1;
};
[
uuid(<GUID>),
helpstring("MyInterface2 Class")
]
coclass MyInterface2
{
[default] interface MyLib.IMyInterface2;
};
[
uuid(<GUID>),
helpstring("MyInterface3 Class")
]
coclass MyInterface3
{
[default] interface MyLib.IMyInterface3;
};
};
I can build this successfully, but when I create a VB 6 project and
select
the server's exe as a reference, the object browser shows no
interfaces in
the server.
What am I doing wrong?
Thanks.
"Alexander Nickolov" wrote:
If you insist on a type library, you have to use #import.
If an IDL is ok with you, don't forget to add its _i.c to
your project (or #include it in a single file as ATL does)
so the linker is happy.
--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@mvps.org
MVP VC FAQ: http://vcfaq.mvps.org
=====================================
"khalprin" <khalprin@discussions.microsoft.com> wrote in message
news:1FE411A4-7012-46FD-87B9-5A6263A54B0A@microsoft.com...
Hello,
I can't seem to get all the details correct to accomplish the
following:
1. Define interfaces in .idl file - In this case there are 5
related
interfaces.
2. Build a type library from the .idl file
3. Use "importlib" in the .idl file of a C++ (ATL) project to
expose
(and
then implement) the 5 interfaces.
4. Build the C++ project without errors.
I can define the interfaces in the .idl file and use midl to
compile
it.
I
can also include a library block in the .idl file to get a type
library
from
it.
I can use "importlib" in the .idl file of the C++ project but the
build
generally results in either unresolved externals for the CLSIDs,
or
errors
about undefined IID_<interface>.
I've tried using the 'Implement interface wizard' in Visual Studio
(2005),
but it puts the interface definition from the typelibrary into the
.idl
file
of the project with no methods or properties. If I have to do
that
manually
I may as well not use the wizard or the external typelibrary.
I want to use the typelibrary approach because these interfaces
will be
implemented in different components and I want to make sure that
components
in VB (and .NET) languages can implement them fairly easily.
Can anyone point out a detailed sample or give me some
step-by-step
instructions?
Thanks.