<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://dougbert.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>Data Transformation Services downloads</title><link>http://dougbert.com/media/g/dts/default.aspx</link><description /><dc:language>en</dc:language><generator>CommunityServer 2008.5 (Build: 30929.2835)</generator><item><title>DTS Custom Task: Office XML Writer</title><link>http://dougbert.com/media/p/59.aspx</link><pubDate>Sat, 21 Jun 2008 20:02:19 GMT</pubDate><guid isPermaLink="false">f9834307-c174-40ff-a2fb-ff80b9231c9e:59</guid><dc:creator>dougbert</dc:creator><slash:comments>0</slash:comments><description>&lt;p&gt;This Zip file contains the Visual Basic.NET source code for a DTS (not SSIS) custom task that I wrote in 2004 and only recently (2008) rediscovered. I wrote this code (1) to learn to write a DTS custom task (2) and to demonstrate how to write out Excel data without using the Excel driver or the Excel application. I threw in creating a Word table just to prove that I could.&lt;/p&gt;
&lt;p&gt;The task lets you choose whether you want a new Excel workbook and worksheet, a new Word document and table, or both. It also lets you choose whether to display the output by launching (1) Notepad to view the XML output as text, or (2) Excel and Word to view the output in the intended applications, or both. Needless to say this latter feature was intended for a development and testing environment, and not for production!&lt;/p&gt;
&lt;p&gt;&lt;img src="http://dougbert.com/cfs-file.ashx/__key/CommunityServer.Components.UserFiles/00.00.00.21.02/customtask.jpg" alt="" /&gt;&lt;/p&gt;
&lt;p&gt;I&amp;#39;m uploading the file since it may be of interest to anyone who still writes DTS custom tasks, or who&amp;#39;s interested in writing out Office XML.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Disclaimers: This isn&amp;#39;t production code, I haven&amp;#39;t upgraded it for the current version of Visual Studio, the Excel and Word XML standard may have evolved (especially Excel), and so forth.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;-Doug&lt;/p&gt;</description><enclosure url="http://dougbert.com/cfs-file.ashx/__key/CommunityServer.Components.PostAttachments/00.00.00.00.59/WriteOfficeXmlTaskRedist.zip" length="1362071" type="application/x-zip-compressed" /></item><item><title>DTS Application Properties</title><link>http://dougbert.com/media/p/26.aspx</link><pubDate>Mon, 26 May 2008 20:40:26 GMT</pubDate><guid isPermaLink="false">f9834307-c174-40ff-a2fb-ff80b9231c9e:26</guid><dc:creator>dougbert</dc:creator><slash:comments>0</slash:comments><description>&lt;p&gt;There&amp;#39;s a dialog box of DTS application-wide settings that disappeared from SQL Server 2005&amp;nbsp;and 2008. It used to live on the context (right-click) menu of the DTS node in&amp;nbsp;SQL Server 2000 Enterprise Manager. One day in a moment of spare time I set about to re-create it for use on a SQL Server 2005 or later computer with DTS support installed. The Visual Basic.NET source code is contained in this file. Here&amp;#39;s now my Windows Form (right) compares to the original DTS dialog on the left...not bad, huh? I even gave it an accurate title!&lt;/p&gt;
&lt;p&gt;&lt;img src="http://dougbert.com/cfs-file.ashx/__key/CommunityServer.Components.UserFiles/00.00.00.21.02/dtsprops_5F00_sxs.jpg" alt="" /&gt;&lt;/p&gt;
&lt;p&gt;I suspect that the &amp;quot;refresh cache&amp;quot; functionality is not useful, because I assume that the data is cached in memory in the process of my little standalone app, and can&amp;#39;t be used by the DTS runtime...but at least you see the DTS API calls.&amp;nbsp;&lt;/p&gt;</description><enclosure url="http://dougbert.com/cfs-file.ashx/__key/CommunityServer.Components.PostAttachments/00.00.00.00.26/DtsProperties.zip" length="74995" type="application/x-zip-compressed" /></item></channel></rss>