<?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>Office Object Model Thoughts</title><link>http://blogs.msdn.com/eric_carter/archive/2004/04/05/107510.aspx</link><description>Currently, one of the greatest obstacles faced by Office developers is the difficulty of using the Office object model. Just calling the object model the &amp;#8220;Office object model&amp;#8221; is incorrect&amp;#8212;it is really several separate object models,</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Office Object Model Thoughts</title><link>http://blogs.msdn.com/eric_carter/archive/2004/04/05/107510.aspx#107526</link><pubDate>Mon, 05 Apr 2004 04:59:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:107526</guid><dc:creator>Thomas Williams</dc:creator><description>Wow Eric, what you are suggesting (your &amp;quot;attractive characteristics&amp;quot;) sounds great! When is .Net for Office...I'm sick of using VBA!&lt;br&gt;&lt;br&gt;Cheers, Thomas&lt;br&gt;</description></item><item><title>re: Office Object Model Thoughts</title><link>http://blogs.msdn.com/eric_carter/archive/2004/04/05/107510.aspx#107704</link><pubDate>Mon, 05 Apr 2004 13:30:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:107704</guid><dc:creator>Jason Dossett</dc:creator><description>Great idea, this is very much needed.  And if Microsoft were to undertake adding this kind of interface, one of the major requirements should be that it can be automated safely from outside the application to allow the server-side automation that Microsoft currently recommends against and doesn't support.</description></item><item><title>re: Office Object Model Thoughts</title><link>http://blogs.msdn.com/eric_carter/archive/2004/04/05/107510.aspx#107728</link><pubDate>Mon, 05 Apr 2004 14:29:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:107728</guid><dc:creator>M</dc:creator><description>The problem with developing for MS office is that Microsoft doesn't provide a &amp;quot;server&amp;quot; version.  For example, if your website needed to create PowerPoint presentations or Excel spreadsheets dynamically, it is just not a good idea to be launching the applications on your server.  So to do this, people end up having to purchase some 3rd party component that does it... and the 3rd party company had to &amp;quot;figure out&amp;quot; the file format, so there's no telling how reliable that would be.  Microsoft is losing out on some big money for not having this.&lt;br&gt;</description></item><item><title>re: Office Object Model Thoughts</title><link>http://blogs.msdn.com/eric_carter/archive/2004/04/05/107510.aspx#109210</link><pubDate>Wed, 07 Apr 2004 18:56:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:109210</guid><dc:creator>Eric Carter</dc:creator><description>I definitely agree that we need to have object models for Office that can be used to create documents on the server.  Turns out that VSTO 2.0 has some features in that area that I will blog about later that let you do some server side programming against Office documents.</description></item><item><title>How I create a Word document Form-letter-like functionality in a web application</title><link>http://blogs.msdn.com/eric_carter/archive/2004/04/05/107510.aspx#110457</link><pubDate>Fri, 09 Apr 2004 18:58:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:110457</guid><dc:creator>Jason Haley</dc:creator><description>How I create a Word document Form-letter-like functionality in a web application</description></item></channel></rss>