Re: Mixing ATL/MFC in VS2005 (reposting as crosspost)

From:

"Alexander Nickolov" <agnickolov@mvps.org>

Newsgroups:

microsoft.public.vc.atl,microsoft.public.vc.mfcole

Date:

Tue, 12 Jun 2007 10:04:59 -0700

Message-ID:

<#GqYQPRrHHA.3248@TK2MSFTNGP03.phx.gbl>

Actually, adding MFC support to an ATL project has _never_
been supported. You can select MFC support for an ATL DLL
on the initial appwizard page, but you can't add MFC support
once you created your ATL project. For an EXE you must
start with an MFC project and later add ATL support.

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

"Brian Muth" <bmuth@mvps.org> wrote in message
news:uyfDNzQrHHA.1508@TK2MSFTNGP05.phx.gbl...

Yeah. Turns out you can add ATL support to an MFC project but not the
other way around.

Not true. Both scenarios are supported.

Now I'm struggling with registration. The reason I asked the original
question is I'm
trying to update my project to not use the deprecated DECLARE_REGISTRY
and instead
use RGS files and needed a sample.

Here's the question now. Do I need to have an RGS file for every
interface,
even the noncreatable ones?

I've heard of non-creatable objects, but not non-creatable interfaces.
Non-creatable objects do not need to be registered.

Brian