Re: Self registering ActiveX control ???

From:

"Alexander Nickolov" <agnickolov@mvps.org>

Newsgroups:

microsoft.public.vc.atl

Date:

Tue, 6 Nov 2007 11:53:07 -0800

Message-ID:

<eytZJ6KIIHA.484@TK2MSFTNGP06.phx.gbl>

While that's the official ActiveX Controls'97 spec, it's widely rejected
by virtually everyone as completely useless. We stick to the OCX'96
spec with the few other additions of value that the '97 spec brought
in (IObjectSafety for example). So an ActiveX Control is a visual
object(*) that implements a slew of interfaces and must be in turn be
hosted by an ActiveX Control Container which in turn implements
a host of services for its controls (*note: an invisible at runtime control
is still visual - it has design-time representation on a form).

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

"Peter Olcott" <NoSpam@SeeScreen.com> wrote in message
news:4tKXi.897$4k.323@newsfe11.phx...

The primary factor that distinguishes an ActiveX control from every other
COM component is self-registration. A scripting language must invoke an
ActiveX control from a ProgId. The ProgId is not available until after the
control is registered.

What is the simplest way for an end-user to register an ActiveX control
that resides in a DLL for use in a scripting language? If the answer is
some sort of install program, then what is the next simplest way that does
not require an install program?