<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Outlook Automation is for People, not for Services.</title><link>http://blogs.msdn.com/b/webdav_101/archive/2008/09/29/outlook-automation-is-for-people-not-for-services.aspx</link><description>I don't know why we see a lot of customers trying to automate Outlook from a service. It’s pretty well documented that it’s a bad idea. Outlook Object Model (OOM) was written for automating Outlook for a user sitting at the box running it. See, Outlook</description><dc:language>en</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator></channel></rss>