<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://dotnet.sys-con.com"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Articles by Rob Harrop</title>
 <link>http://dotnet.sys-con.com/</link>
 <description>Latest articles from Rob Harrop</description>
 <language>en</language>
 <copyright>Copyright 2008 SYS-CON Media</copyright>
 <generator>SYS-CON Media</generator>
 <lastBuildDate>Tue, 07 Oct 2008 02:35:01 EDT</lastBuildDate>
 <docs>http://backend.userland.com/rss</docs>
 <ttl>10</ttl>
<item>
 <title>Wise for Visual Studio .NET</title>
 <link>http://dotnet.sys-con.com/node/38961</link>
 <description>Perhaps the most important, yet most overlooked, area of application development is that of deployment. A flawed installation, or worse - one that corrupts other applications - does not instill faith in your software and makes for very unhappy clients. Having been in this situation myself, I took the time to investigate the various utilities available for creating Windows Installer-based setup applications.&lt;p&gt;&lt;a href=&quot;http://dotnet.sys-con.com/node/38961&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Thu, 11 Sep 2003 14:15:12 EDT</pubDate>
 <guid isPermaLink="true">http://dotnet.sys-con.com/node/38961</guid>
</item>
</channel>
</rss>
