No version of Outlook should ever be run in a Windows service. It's not that
it's not a good idea, it's a really bad idea. Outlook puts up all sorts of
user prompts and there's no way to disable them. That's aside from the user
impersonation issues. You'll never find anyone who recommends using Outlook
in a service. If you must do something like that use CDO 1.21 or Extended
MAPI or Redemption instead in the service.

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Absolute Beginner's Guide to Microsoft Office Outlook 2003
Reminder Manager, Extended Reminders, Attachment Options
http://www.slovaktech.com/products.htm


"Tony Gravagno" wrote in message
...
Thanks Dmitry! Well, a licensed instance of Outlook can be used from
a Windows service, it's just not a good idea. What's the alternative?
I've written apps that ran in the Windows tray to keep them
unobtrusive, but my users didn't like them because they needed to have
a user logged-in all the time in order to use them. I can easily
shift this code into an add-in (it's already encapsulated for this
sort of thing) which only gets run when someone is running Outlook,
maybe when they click a button. But what if that person is on
vacation? - These tasks may not get done for a couple weeks. As an
unattended service this process is independent of individuals.

Does anyone know if Outlook 2007 or some other tool (VSTO?) is better
for doing this sort of unattended, user-independent operation?

Regards,
Tony