Re: Creating object inside an ISAPI DLL - does registry settings required?

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Alexander Nickolov (agnickolov_at_mvps.org)
Date: 06/26/04 

Date: Sat, 26 Jun 2004 14:25:11 -0700

Yes, you are correct. In addition, IDispatchImpl can _only_
be used to implement dual interfaces. Any other kind of dispatch
interface needs hand-coding in ATL. 

-- 
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@mvps.org
MVP VC FAQ: http://www.mvps.org/vcfaq
=====================================
"Jennifer Lopez" <jen.lo@changepoint.com> wrote in message
news:erj91%235WEHA.2840@TK2MSFTNGP11.phx.gbl...
> Hi all,
>
> I have a legacy ActiveX control and now I want to implement an ISAPI
> extension DLL which read parameters from the query string and generate
> images sending back to browsers. I am thinking adding function on top of
the
> ActiveX implementation so the same DLL can server both purposes (that will
> save a lot of maintenance work!). Considering that many web server are
> running in the shared space, I want to make the system impact minimum
(i.e.
> the ISAPI Dll does not utilize any sytem resources such as registry).
>
> I am able to create the object directly by calling something like this:
> CComObjectStack<CMyActiveXControl> object;
>
> In this way the ActiveX dll need not registered. In the next step I want
to
> be able to call the IDispatch interface on this object, passing the
> properties received from the query string/form fields. I wonder whether it
> is possible to do this without registering the object - it looks that the
> ATL IDispatch implementation is based on type library, which requires
> registration.
>
> Any one can tell me my assertion here is correct? Thanks a lot.
>
>
>
>

Relevant Pages

  • Re: MULTI_QI
    ... >> So to have client be able dynamically load some COM dll, ... Imagine you are given a DLL implementing ... >> interface is to provide a way to discover what SERVER has to offer.... ... > Again, look at IDispatch. ...
    (microsoft.public.vc.atl)
  • Re: Probleme mit meinem erstes Com-Objekt
    ... > Dort braucht man meines Wissens aber das IDispatch Interface (und ... IDispatch ist nur für ActiveX-Controls notwendig, ... ich soll unter Basic mit CoTaskMemAlloc den Speicherbereich ... ich die Einstellungen in der Registry komplett von Hand ...
    (microsoft.public.de.vc)
  • Re: Consuming a .NET class exposed through COM?
    ... in the Registry. ... Then the class needs to implement an Interface that has a ... Generating a strong name key file ... but it fails to open the DLL with a walkback ...
    (comp.lang.smalltalk.dolphin)
  • Re: DLL registering problem in WinCE..
    ... The *interface* wouldn't be in the registry. ... Use debug messages to see what pieces of your DLL ... >> Paul T. ...
    (microsoft.public.windowsce.embedded.vc)
  • Re: .NET and COM
    ... The entry point sits in the main DLL but depending on the needed instruments one of the AddOn-DLL?s is loaded. ... Every DLL exports a special interface (IOleInstrument). ... In case of C++ this interface is registered as IOleInterface in the registry but in case of the C# DLL the interface is registered as RdrOle4AddOn6.Instrument (which is a combination of the name of the namespace ...
    (microsoft.public.dotnet.languages.csharp)