Re: Start sequence of an ATL service

From:

"Igor Tandetnik" <itandetnik@mvps.org>

Newsgroups:

microsoft.public.vc.atl

Date:

Mon, 21 May 2007 16:52:11 -0400

Message-ID:

<uqdwxn#mHHA.3520@TK2MSFTNGP04.phx.gbl>

Ignacio Burgue?o <blabla@blabla.com> wrote:

My CServiceModule::Run() method (I'm on VC6 and ATL3) looks something
like this:

HRESULT hr = CoInitializeEx(NULL, COINIT_MULTITHREADED);
...
hr = _Module.RegisterClassObjects(CLSCTX_LOCAL_SERVER |
CLSCTX_REMOTE_SERVER, REGCLS_MULTIPLEUSE);
...
[lengthy startup code here]
SetServiceStatus(SERVICE_RUNNING);

then, the message loop.

So, it seems that my assumption that the service is able to 'service'
objects only when running the message loop is wrong (surely because I
entered the MTA). How can I guarantee that any object will be created
only after my startup code has run?

Put RegisterClassObjects call after initialization. Make sure
initialization takes less than 30sec, or CoCreateInstance call on the
client side will time out and fail.
--
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