views:

66

answers:

1

I recently created a windows service which can wear various hats depending on what it needs to do. One of these hats is the ability to create update and delete outlook contacts on an exchange server. Before the windows service, the application ran as a windows app and used the outlook interop to get the job done. As a windows service that doesn't seem possible.

Now I'm looking at trying to go straight to Exchange to get the job done. Any hints or tips as far as what's the best way to communicate directly with Exchange, or any issues that may arise would be greatly appreciated.

+1  A: 

You'll want to go to the Exchange Server Developer Center to get more info on this.

Given your requirements, and since you're using C#, the Exchange Web Services Managed API is probably your best option.

Reed Copsey
While exchange was installing I took some more stabs at getting our old outlook interop code working. After some fooling around it appears to function without the need of writing new code to talk directly to Exchange. Essentially we needed to make the service run as a user that has an outlook profile set up. System Local apparently didn't. :Pdo you think there Would be any significant benefits to talk straight to exchange at this point?
Buddy Lee
Communicating directly with exchange has 2 advantages: You don't need a user account, and you'll get much better performance, since you're removing the interop layer. You also can do more things that aren't allowable via Outlook's API, since you have the full exchange API available.
Reed Copsey