Re: Using same interfaces for in-proc vs. out-proc
Drew wrote:
I've set up a minimal example, minus the static LIB for the EXE. IOW, =
source
for the COM part is in the same project as the rest of the EXE code. =
The DLL
points to the same source as the EXE project for the COM portion of =
the
project. I can compile and link both projects but I'm unable to =
register the
DLL. When I run it through Dependency Walker and profile it with =
regsvr32 I
get Error 0x80070716 "The specified resource name cannot be found in =
the
image file".
Find CAtlComModule::RegisterServer call (in a DLL project it's in =
DllRegisterServer; in EXE, I don't remember off the top of my head). =
Pass FALSE for the first parameter (the wizard-generated code passes =
TRUE). Since you no longer bind a TLB as a resource, you can't register =
it this way.
The EXE registers fine and I'm able to use it from a VB
project.
Apparently, you still bind the TLB (which is now supposed to be =
standalone) as a resource to your EXE. Check your .rc file.
--
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