<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Creating Software Installers</title>
	<atom:link href="http://www.directoratnight.com/2009/02/22/creating-software-installers/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.directoratnight.com/2009/02/22/creating-software-installers/</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Tue, 19 Apr 2011 13:47:08 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.1</generator>
	<item>
		<title>By: ahoeben</title>
		<link>http://www.directoratnight.com/2009/02/22/creating-software-installers/comment-page-1/#comment-3564</link>
		<dc:creator>ahoeben</dc:creator>
		<pubDate>Mon, 23 Feb 2009 08:32:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.directoratnight.com/?p=198#comment-3564</guid>
		<description>On the PC-side I would recommend NSIS, mainly for its scriptability and small installers:
http://nsis.sourceforge.net
I once made a working (slim) Shockwave installer as a technical proof of concept that was less than a Mb.

It&#039;s got a steep learning curve, but once you&#039;ve got it set up, it&#039;s hard te beat. Especially in a more-or-less automated build system.</description>
		<content:encoded><![CDATA[<p>On the PC-side I would recommend NSIS, mainly for its scriptability and small installers:<br />
<a href="http://nsis.sourceforge.net" rel="nofollow">http://nsis.sourceforge.net</a><br />
I once made a working (slim) Shockwave installer as a technical proof of concept that was less than a Mb.</p>
<p>It&#8217;s got a steep learning curve, but once you&#8217;ve got it set up, it&#8217;s hard te beat. Especially in a more-or-less automated build system.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

