Re: IDL enum definition not exported in the DLL
I didn't see any reference to attributed ATL in the post.
Seems straight IDL to me, albeit with weird attribute
placement due to the typedef.
To OP: get rid of the typedef. And mention the enum in
the library section of your IDL.
--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@mvps.org
MVP VC FAQ: http://vcfaq.mvps.org
=====================================
"Brian Muth" <bmuth@mvps.org> wrote in message
news:uCeKEJX6HHA.5184@TK2MSFTNGP03.phx.gbl...
I suggest you switch to unattributed ATL, which should give you much
greater control over what the MIDL uses as source.
Attributed ATL is very buggy anyway, and should be avoided for that reason
alone. None of the experience people who frequent this newsgroup uses
attributed ATL.
Brian
"Axel Bock" <axel.bock.news@googlemail.com> wrote in message
news:1188301057.460303.171280@57g2000hsv.googlegroups.com...
Hi group,
I have a COM DLL which exports some types. Among those types are two
enumerations, which declared like shown below. Alas this does not work
quite as expected. The first enum gets exported all right, whereas the
second one cannot be found in the final DLL.
I researched a bit and it seemed that the enum is not exported cause
it is not referenced from the DLL itself. So I wrote a dummy interface
which uses this enumeration, but to no avail. But I need to export the
enumeration so that client modules can use it.
Any ideas what I do wrong here? I really don't get it ...
Thanks in advance & greetings,
Axel.
------------------------------ snip ------------------------------
[ v1_enum, public ]
typedef [public] enum {
SERVICESCOPE_PUBLIC = 0,
SERVICESCOPE_CONTAINER = 1,
SERVICESCOPE_MODULE = 2
} ServiceScope;
[ v1_enum, public ]
typedef [public] enum {
CONTEXTSCOPE_CONTAINER = 1,
CONTEXTSCOPE_MODULE = 2,
CONTEXTSCOPE_SERVICE = 3,
CONTEXTSCOPE_SESSION = 4
} ContextScope;