Old style Exchange extensions are written only using Extended MAPI (C++ or
Delphi only), use an ECF file for configuration and work with all versions
of Outlook. COM addins can be written in any high-level language that
supports COM and are supported for only Outlook 2000 or later. They can be
written using the Outlook object model, Extended MAPI, CDO 1.21 and so on.
True...
But I came accross the add-in which is neither following the COM add-in
model/architecture nor using the ECF file. But it is using the Exchange
client extension model. And that's where I got confused that the addin is
following Exchange client extension model and not using the ECF file.
Could you please elaborate on this?
Regards
CC
I have no idea. Exchange client extensions use ECF files. Since I don't
write Exchange extensions I don't know if you can have one without an ECF.
You can probably check that on MSDN.
Ask a Question
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.