DLL won't register

[Drew]

I'm trying to apply what I learned in the thread "Using same interfaces for
in-proc vs. out-proc" to convert real world COM servers to use the same TLB.
I can't seem to get the DLL to work. The EXE and DLL differ only in the
coclass for the only creatable interface CLSID (Application in EXE,
ApplicationX in DLL). The CLSID for the DLL doesn't show up in the registry.
I'm calling _AtlModule.RegisterServer(FALSE) in the DLL and removed the
TYPELIB from the RC file and added REGISTRY lines for the RGS files which
are DLLName.rgs and ApplicationX.rgs. The DLL project has no IDL file and
doesn't build a TLB. Do I still need to specifically register the DLL to get
the CLSIDs into the registry (just tried it and it didn't work)? I don't
remember having to do this in my minimal version. What is the proper
mechanism for getting my CLSID for ApplicationX into the registry?

Thanks,
Drew

[Igor Tandetnik]

Drew <d...@dam.com> wrote:
> I'm trying to apply what I learned in the thread "Using same
> interfaces for in-proc vs. out-proc" to convert real world COM
> servers to use the same TLB. I can't seem to get the DLL to work. The
> EXE and DLL differ only in the coclass for the only creatable
> interface CLSID (Application in EXE, ApplicationX in DLL). The CLSID
> for the DLL doesn't show up in the registry. I'm calling
> _AtlModule.RegisterServer(FALSE) in the DLL and removed the TYPELIB
> from the RC file and added REGISTRY lines for the RGS files which are
> DLLName.rgs and ApplicationX.rgs.

Check that you have OBJECT_ENTRY[_AUTO] for each coclass, and that the coclass has a DECLARE_REGISTRY_RESOURCEID or similar declaration pointing to the correct resource. If everything checks, you can always step through RegisterServer call under debugger and see where it fails.
--
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

[Drew]

Thanks Igor. I had some resource IDs out of sync.

Thanks,
Drew

"Igor Tandetnik" <itand...@mvps.org> wrote in message
news:eP77YgK...@TK2MSFTNGP06.phx.gbl...