Re: COM object data persistence
From: Kim Gräsman (kim_at_mvps.org)
Date: 04/21/04
- Next message: Igor Tandetnik: "Re: The difference between propput and propputref in IDL"
- Previous message: Egbert Nierop \(MVP for IIS\): "Re: Memory usage in Exe server"
- In reply to: Frank: "Re: COM object data persistence"
- Next in thread: Frank: "Re: COM object data persistence"
- Reply: Frank: "Re: COM object data persistence"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 21 Apr 2004 19:12:28 +0200
Hi Frank,
> But when I tried to use my Window Service COM client to access that
> common data, I found the common data is not the same as the VB, MFC
> clients accessed. Also when I looked at Task Manager, I found my EXE
> was running in two copies(two processes). So why would this happen? I
> guess it related to Terminal/Desktop or User account context problem.
> But my service is running in the same account as my VB, MFC client.
>
> I don't understand that in what situation the system will load the
> COM exe again while there is already one copy running in the system?
It sounds like your service isn't configured as a service.
ATL services have the somewhat weird option of being registered either as
regular out-of-process COM servers (with /regserver) or as services (with
/service) - which did you do?
Also, I believe you need to register your class objects with the
REGCLS_MULTIPLEUSE flag (see call to _Module.RegisterClassObjects)
-- Best regards, Kim Gräsman
- Next message: Igor Tandetnik: "Re: The difference between propput and propputref in IDL"
- Previous message: Egbert Nierop \(MVP for IIS\): "Re: Memory usage in Exe server"
- In reply to: Frank: "Re: COM object data persistence"
- Next in thread: Frank: "Re: COM object data persistence"
- Reply: Frank: "Re: COM object data persistence"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|