<?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>Running packages from custom applications</title><link>http://blogs.msdn.com/mattm/archive/2007/09/14/running-packages-from-custom-applications.aspx</link><description>There are a lot of different ways to run SSIS packages , and many situations call for a custom package launcher application. If you're coding your own launcher, one thing to keep in mind is that certain SSIS functionality (such as the Script task / component)</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Configuring .NET for running SSIS packages from custom applications</title><link>http://blogs.msdn.com/mattm/archive/2007/09/14/running-packages-from-custom-applications.aspx#8212738</link><pubDate>Sat, 15 Mar 2008 02:16:26 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8212738</guid><dc:creator>Michael Entin's notebook</dc:creator><description>&lt;p&gt;.NET configuration is usually performed using .exe.config files, so it is a just matter of providing good config file. How do you know what is good? The simplest way is to look at the config file that SSIS provides, and copy the appropriate settings.&lt;/p&gt;
</description></item></channel></rss>