Re: Using same interfaces for in-proc vs. out-proc
- From: "Drew" <dam@xxxxxxx>
- Date: Mon, 16 Nov 2009 13:57:16 -0600
"Igor Tandetnik" <itandetnik@xxxxxxxx> wrote in message
news:OOY9ENvZKHA.2184@xxxxxxxxxxxxxxxxxxxxxxx
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.
Yes, that's true. I've removed the TYPELIB statement from both EXE and DLL
projects and registered the TLB using regtlib. I also removed the REGISTRY
statements from the RC files. Should I have? Anyway, I still have the same
problem. This works:
Dim myapp As COMServerALib.Application
Set myapp = New COMServerALib.Application
Dim name As String
name = myapp.name
This doesn't:
Dim myapp As COMServerALib.ApplicationX
Set myapp = New COMServerALib.ApplicationX ' ActiveX component can't
create object
Dim name As String
name = myapp.name
Any ideas?
Thanks again,
Drew
.
- Follow-Ups:
- Re: Using same interfaces for in-proc vs. out-proc
- From: Igor Tandetnik
- Re: Using same interfaces for in-proc vs. out-proc
- References:
- Using same interfaces for in-proc vs. out-proc
- From: Drew
- Re: Using same interfaces for in-proc vs. out-proc
- From: Igor Tandetnik
- Re: Using same interfaces for in-proc vs. out-proc
- From: Drew
- Re: Using same interfaces for in-proc vs. out-proc
- From: Igor Tandetnik
- Re: Using same interfaces for in-proc vs. out-proc
- From: Drew
- Re: Using same interfaces for in-proc vs. out-proc
- From: Igor Tandetnik
- Re: Using same interfaces for in-proc vs. out-proc
- From: Drew
- Re: Using same interfaces for in-proc vs. out-proc
- From: Igor Tandetnik
- Re: Using same interfaces for in-proc vs. out-proc
- From: Drew
- Re: Using same interfaces for in-proc vs. out-proc
- From: Igor Tandetnik
- Re: Using same interfaces for in-proc vs. out-proc
- From: Drew
- Re: Using same interfaces for in-proc vs. out-proc
- From: Igor Tandetnik
- Re: Using same interfaces for in-proc vs. out-proc
- From: Drew
- Re: Using same interfaces for in-proc vs. out-proc
- From: Igor Tandetnik
- Re: Using same interfaces for in-proc vs. out-proc
- From: Drew
- Re: Using same interfaces for in-proc vs. out-proc
- From: Igor Tandetnik
- Re: Using same interfaces for in-proc vs. out-proc
- From: Drew
- Re: Using same interfaces for in-proc vs. out-proc
- From: Igor Tandetnik
- Re: Using same interfaces for in-proc vs. out-proc
- From: Drew
- Re: Using same interfaces for in-proc vs. out-proc
- From: Drew
- Re: Using same interfaces for in-proc vs. out-proc
- From: Igor Tandetnik
- Re: Using same interfaces for in-proc vs. out-proc
- From: Drew
- Re: Using same interfaces for in-proc vs. out-proc
- From: Igor Tandetnik
- Re: Using same interfaces for in-proc vs. out-proc
- From: Drew
- Re: Using same interfaces for in-proc vs. out-proc
- From: Igor Tandetnik
- Using same interfaces for in-proc vs. out-proc
- Prev by Date: Re: Using same interfaces for in-proc vs. out-proc
- Next by Date: Re: Using same interfaces for in-proc vs. out-proc
- Previous by thread: Re: Using same interfaces for in-proc vs. out-proc
- Next by thread: Re: Using same interfaces for in-proc vs. out-proc
- Index(es):
Relevant Pages
|