Make Add In available through OWA?

[Brian McCullough]

Hello,

I have created a custom add in and have it working with Outlook XP. Is it
possible to create a front end for a COM Add In and expose it through OWA?

From what I understand OWA is hosted in IIS and is exposed through some
standard web code pages (i.e HTML, JavaScript). I would imagine any
development would need to be done through JavaScript functions. Does this
sound correct?

Does this break the support agreement with Microsoft if you customize OWA?

Sorry if this is the wrong group...If so, please point me to a more
appropriate group!

Thanks!

 

[Ken Slovak - [MVP - Outlook]]

OWA development would be more of an Exchange development topic and something
like microsoft.public.exchange.development would be more appropriate.

You are correct about customizing OWA with javascript, but it must be done
separately for each version of Exchange, each SP and each time they change
something. So it's not a static target. In addition, OWA code runs on the
server and has no knowledge of client side code such as a COM addin. When
you run OWA you are running it on IE (or some other browser), not in
Outlook. You can access OWA from a kiosk machine for example, where no
Outlook at all is installed. How would you provide a front end for an addin
in cases like that?

Customizing OWA is always unsupported, but my Exchange developer friends
have been doing it for years.