Re: exposing interfaces
- From: "Alexander Nickolov" <agnickolov@xxxxxxxx>
- Date: Wed, 18 Jan 2006 10:24:37 -0800
The frst step is to carefully state what do you need to accomplish
(requirements analysis). The next step is to plan your object
hierarchy (architectural design). Then you need to specify the
actual interfaces implemented by those objects (detailed architectural
design). Then you need to map your interface design to your
current system (system architecture). Then you specify the actual
classes that implement it (detailed system design). Only then can you
proceed with implementation.
--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@xxxxxxxx
MVP VC FAQ: http://www.mvps.org/vcfaq
=====================================
"Dur" <Dur@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8A8C1ADB-53A6-47F3-A8E3-AD2CBC854520@xxxxxxxxxxxxxxxx
> Hi,
>
> I am planning to create COM EXE(COM Component) like Outlook.exe.
> I want to expose some interfaces like _IDTExtensibility2.Can anybody give
> brief idea on this? How can I expose interfaces with some functionality
> like
> OnConnection has Application pointer?
>
> What are the steps to follow to do this?
> I read Inside COM.
>
> Regards,
> --
> Dur.
.
- Follow-Ups:
- Re: exposing interfaces
- From: Dur
- Re: exposing interfaces
- Prev by Date: Re: out param question
- Next by Date: RE: Memory ownership, parameters, variants, etc.
- Previous by thread: Re: failed to deploy DLL in ActiveX control
- Next by thread: Re: exposing interfaces
- Index(es):
Relevant Pages
|