Re: Extending ATL COM Object Dual Interfaces

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

  • Next message: Alexander Nickolov: "Re: Creating object inside an ISAPI DLL - does registry settings required?"
    Date: Sat, 26 Jun 2004 14:22:43 -0700
    
    

    Seems pretty standard to me, providing you have the source code.
    Not sure if you can do it in VB without breaking COM rules, but
    in C++/ATL it's rather straightforward. You derive a new dual
    interface from the old one, then implement it. These FAQ articles
    should give you the idea how it is done in source:

    http://www.mvps.org/vcfaq/com/7.htm
    http://www.mvps.org/vcfaq/com/8.htm

    -- 
    =====================================
    Alexander Nickolov
    Microsoft MVP [VC], MCSD
    email: agnickolov@mvps.org
    MVP VC FAQ: http://www.mvps.org/vcfaq
    =====================================
    "Doug C. Mace" <dcmace3@NOSPAMadelphia.net> wrote in message
    news:a_KdnWqJ_dcXGEDdRVn-vg@adelphia.com...
    > Alexander or Igor,
    >
    > I have a need to extend existing CoClass functionality with dual
    interfaces
    > and searching for viable solutions. I discovered a April 1999, Windows
    > Developer Journal article by Howard Silver titled "Extending ATL COM
    > Objects". Are you familiar with this article? I tried the solution in VB
    and
    > it seems work but need an opinion to determine if it contains any flaws or
    > breaks COM rules. I didn't want to post the entire article and solution in
    > the group since its lengthy. However, I can zip up the article and code
    > snippets and transmit to either of you experts if you have private email.
    >
    > Can't seem to find a lot of information on the subject so looking for
    > sources of information. Also, the CoClass must contain dual interfaces to
    > support scripting clients as well as vTable support for early binding.
    >
    > Your help would be greatly appreciated.
    >
    > Doug
    >
    >
    >
    >
    

  • Next message: Alexander Nickolov: "Re: Creating object inside an ISAPI DLL - does registry settings required?"

    Relevant Pages

    • Re: Fedora Desktop future- RedHat moves
      ... I could have gotten a copy of the source code that it's own author and the experts involved in the OS packaging couldn't fix. ... But if you walk away from your interfaces particularly without supplying replacements for the things that will break, no one can be expected to trust you. ... I do recall reading about some issues with firewire but never ...
      (Fedora)
    • Re: CLR details- Are MSCorEE.dll and MSCorWks.dllMSCorSvr.dll COM
      ... I'm having a source code license and I'm not interested ... Also tlb files do not ... necessarily represent accurately the COM interfaces of a COM server, ...
      (microsoft.public.dotnet.framework.clr)
    • Re: [PATCH] char: Add Dell Systems Management Base driver
      ... > systems management software that access the interfaces are ... > source code for the software. ... > following Dell proprietary hardware systems management interfaces: ...
      (Linux-Kernel)
    • Re: One good argument against using "with"
      ... Is there any reason those interfaces couln't be made TPersistent ... not possible to re-generate the source code using these interfaces. ... It also has a Descendants property. ...
      (borland.public.delphi.non-technical)