<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.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>Don’t Use Office Applications (or GDI+, or System.Drawing, or WinInet) in a Server Application (or ASP.Net)</title><link>http://blogs.technet.com/tristank/archive/2008/11/06/don-t-use-office-applications-or-gdi-or-system-drawing-or-wininet-in-a-server-application-or-asp-net.aspx</link><description>Johan posted a timely reminder of a long-standing perennial support call generator in his post Office Automation . Adding one more option to the list of possible workarounds – direct XML-based production/manipulation of an OOXML (or ODF, for that matter)</description><dc:language>en-AU</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Don???t Use Office Applications (or GDI+, or System.Drawing, or WinInet) in a Server Application (or ASP.Net) | MS Tech News</title><link>http://blogs.technet.com/tristank/archive/2008/11/06/don-t-use-office-applications-or-gdi-or-system-drawing-or-wininet-in-a-server-application-or-asp-net.aspx#3148336</link><pubDate>Thu, 06 Nov 2008 10:32:53 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3148336</guid><dc:creator>Don???t Use Office Applications (or GDI+, or System.Drawing, or WinInet) in a Server Application (or ASP.Net) | MS Tech News</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://mstechnews.info/2008/11/don%e2%80%99t-use-office-applications-or-gdi-or-systemdrawing-or-wininet-in-a-server-application-or-aspnet/"&gt;http://mstechnews.info/2008/11/don%e2%80%99t-use-office-applications-or-gdi-or-systemdrawing-or-wininet-in-a-server-application-or-aspnet/&lt;/a&gt;&lt;/p&gt;
</description></item></channel></rss>