Re: Avoid lazy instantiation for singletons?

From:

"Alexander Nickolov" <agnickolov@mvps.org>

Newsgroups:

microsoft.public.vc.atl

Date:

Thu, 30 Nov 2006 17:32:12 -0800

Message-ID:

<eOcvHiOFHHA.1188@TK2MSFTNGP06.phx.gbl>

Well, I guess it won't hurt to point the obvious - do not use
a COM singleton... A simple C++ singleton with your
COM classes delegating to it would have left you with
nothing to do after changing the libraries along with the
compiler. Hindsight is easy, isn't it? The trick is to turn
it into foresight for the next project...

--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@mvps.org
MVP VC FAQ: http://www.mvps.org/vcfaq
=====================================

"Vanja" <vanja@damn-you-spam.net> wrote in message
news:DBFA65E7-9113-4647-A44D-C737656CB96B@microsoft.com...

Hi everybody,

I have several COM Servers that I migrated from Visual Studio 6 to 2005.
They are singletons. In VS6, the single instance of the COM-object was
created immediately when the process was started and my object went in
FinalConstruct right away, but in VS2005 (newer ATL-version) singletons
are
instantiated "lazy" (when the first client calls CoCreateInstance).
Is there a fancy option to force the "old" (non-lazy) way of instantiation
in VS2005? Calling CoCreateInstance on itself seems messy, and i don't
feel
like rewriting all of my servers. I'm already working on a custom class
factory, but if someone knows an easier way, please share!

Thanks!
Vanja