Re: Migrating COM dll from ATL3 to ATL7
- From: "Igor Tandetnik" <itandetnik@xxxxxxxx>
- Date: Wed, 30 Mar 2005 20:07:20 -0500
"Aaron" <aaron-friesen@xxxxxxxxxxx> wrote in message
news:ue6w4lYNFHA.3356@xxxxxxxxxxxxxxxxxxxx
> I have a COM dll originally developed using VC++ 6 now
> compiling under VC++ .NET. I am getting lots of C4996
> warnings that ATL::CComModule::UpdateRegistryClass has
> been deprecated.
>
> The warning stems from using the DECLARE_REGISTRY macro,
> but I cannot find how this should be replaced.
The common way is to write a registration script (.rgs file), bind it as
a resource to your executable, and refer to it with
DECLARE_REGISTRY_RESOURCEID macro. Use the wizard to generate a new
project (remember to uncheck the Attributed checkbox) and insert a
simple COM object, just to see what an .rgs file looks like.
--
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
.
- Follow-Ups:
- Re: Migrating COM dll from ATL3 to ATL7
- From: Aaron
- Re: Migrating COM dll from ATL3 to ATL7
- References:
- Migrating COM dll from ATL3 to ATL7
- From: Aaron
- Migrating COM dll from ATL3 to ATL7
- Prev by Date: Migrating COM dll from ATL3 to ATL7
- Next by Date: Re: How to receive events from an EXE connectable object?
- Previous by thread: Migrating COM dll from ATL3 to ATL7
- Next by thread: Re: Migrating COM dll from ATL3 to ATL7
- Index(es):
Relevant Pages
|