Interfaces to MS Exchange/Outlook to add Calendar appointments or

My organization currently has interfaces in place to generate MS Outlook
emails from our business applications. I am trying to determine if it is
possible and how difficult it might be to interface with MS Ecxhange or
Outlook from a business application and add items to a user's calendar, task
list, or at a minimum to set a follow up flag in an email.

We are running Exchange 2003 and a variety of MS Outlook 2000 and 2003. We
do have plans to upgrade to Office/Outlook 2007 in the near future and I'm
not sure when an exhange server upgrade is being planned for. So the
solution we put in place will need to be upward compatible for when we
upgrade.
--
EM

Henning
Wed Mar 12 15:07:05 CDT 2008

Hi,

how do you plan to access Exchange? Does your application now depend on an
opened Outlook to create mails?

Do you want to be able to add contacts and other items when Outlook is
closed?

You can use Outlook Interop to access the current logged on profile.

To access Exchange from a managed app, you could use WebDAV, which is
basically an extension to the HTTP protocol. I have a C# wrapper on my
website (www.infinitec.de) and there are other available on the net.

Kind regards,
Henning Krause


"EMcCarthy" <EMcCarthy@discussions.microsoft.com> wrote in message
news:9CEFA2E7-2377-4D8C-92B0-A53808E7A70E@microsoft.com...
> My organization currently has interfaces in place to generate MS Outlook
> emails from our business applications. I am trying to determine if it is
> possible and how difficult it might be to interface with MS Ecxhange or
> Outlook from a business application and add items to a user's calendar,
> task
> list, or at a minimum to set a follow up flag in an email.
>
> We are running Exchange 2003 and a variety of MS Outlook 2000 and 2003.
> We
> do have plans to upgrade to Office/Outlook 2007 in the near future and I'm
> not sure when an exhange server upgrade is being planned for. So the
> solution we put in place will need to be upward compatible for when we
> upgrade.
> --
> EM

EMcCarthy
Thu Mar 13 07:20:01 CDT 2008

Thank you for your response.

Our current applications do both methods of sending emails - some do this as
a background process in the evening (Oracle Server and SMTP client) and do
not rely on a user's instance of MS Outlook being open. Other applications
just launch the equivalent of a new message in a user's instance of Outlook
and the user hits send to send the message.

For the purpose of adding Calendar and Task items, we would want this to be
a background process which runs are various times of the day and it not tied
to a specific user being signed on the application or MS Outlook.

--
EM


"Henning Krause [MVP - Exchange]" wrote:

> Hi,
>
> how do you plan to access Exchange? Does your application now depend on an
> opened Outlook to create mails?
>
> Do you want to be able to add contacts and other items when Outlook is
> closed?
>
> You can use Outlook Interop to access the current logged on profile.
>
> To access Exchange from a managed app, you could use WebDAV, which is
> basically an extension to the HTTP protocol. I have a C# wrapper on my
> website (www.infinitec.de) and there are other available on the net.
>
> Kind regards,
> Henning Krause
>
>
> "EMcCarthy" <EMcCarthy@discussions.microsoft.com> wrote in message
> news:9CEFA2E7-2377-4D8C-92B0-A53808E7A70E@microsoft.com...
> > My organization currently has interfaces in place to generate MS Outlook
> > emails from our business applications. I am trying to determine if it is
> > possible and how difficult it might be to interface with MS Ecxhange or
> > Outlook from a business application and add items to a user's calendar,
> > task
> > list, or at a minimum to set a follow up flag in an email.
> >
> > We are running Exchange 2003 and a variety of MS Outlook 2000 and 2003.
> > We
> > do have plans to upgrade to Office/Outlook 2007 in the near future and I'm
> > not sure when an exhange server upgrade is being planned for. So the
> > solution we put in place will need to be upward compatible for when we
> > upgrade.
> > --
> > EM
>
>