Re: Using same interfaces for in-proc vs. out-proc
Drew <dam@dam.com> wrote:
I'm worried that the IID assigned to the Application
interface, which is the only one directly creatable by a client would
somehow reference the LIBID in such way that having both EXE and DLL
registered at the same time would not be possible which is what you
seem to be describing.
An interface can only refer to one LIBID at a time. It doesn't matter =
how the type library behind that LIBID is physically packaged, as long =
as it actually exists on the machine. It could be in a separate TLB =
file, or attached as a resource to the server that implements the =
interface, or attached as a resource to some unrelated EXE or DLL.
If you have the same type library, with the same LIBID, attached both to =
the EXE and the DLL, then the registry entries would point to whichever =
of them was registered last. This is not a problem in itself. There are =
two issues with this. A minor one - you have a copy of a type library =
that is not being used, so why have it in the first place? A major one - =
if you uninstall the module that LIBID registry entries point to, the =
other module will stop working (or, you will have to take care to =
re-register it).
The reason for having these two identical forms of the server is
because a customer requested to have a version with no GUI (even
though visibility of the GUI is optional).
I don't quite see how the presence of a GUI is related to whether the =
server is an EXE or a DLL.
--
With best wishes,
Igor Tandetnik
With sufficient thrust, pigs fly just fine. However, this is not =
necessarily a good idea. It is hard to be sure where they are going to =
land, and it could be dangerous sitting under them as they fly overhead. =
-- RFC 1925