<?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"
	>
<channel>
	<title>Comments on: BoxedApp SDK 2.0.1, BoxedApp Packer 2.1.1</title>
	<atom:link href="http://boxedapp.com/blog/2009/01/31/boxedapp-sdk-201-boxedapp-packer-211/feed/" rel="self" type="application/rss+xml" />
	<link>http://boxedapp.com/blog/2009/01/31/boxedapp-sdk-201-boxedapp-packer-211/</link>
	<description>BoxedApp: Tips'n'Tricks, Examples, Use Cases etc.</description>
	<pubDate>Thu, 29 Jul 2010 21:40:08 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: MLefebvre</title>
		<link>http://boxedapp.com/blog/2009/01/31/boxedapp-sdk-201-boxedapp-packer-211/#comment-7</link>
		<dc:creator>MLefebvre</dc:creator>
		<pubDate>Thu, 05 Feb 2009 19:45:39 +0000</pubDate>
		<guid isPermaLink="false">http://boxedapp.com/blog/?p=11#comment-7</guid>
		<description>We wanted to make a "Packed" version of our application, mainly for demo purposes (one single EXE with all data files embedded and no "installation" required). For that we had some particular needs : our application requires various service files, whose names and locations (at runtime) depend on the actual EXE name and/or location, and therefore are not fully predictable at build time.

That feature (env variables in BoxedApp Packer) allowed us to answer very easily to those needs, that would have otherwise require some scripting or additional developments. Finally, we did not have to change one single bit in our original EXE. I can also testify that the BoxedApp product team has been quite efficient, with a cycle time of a few hours (well, maybe you know some software companies who have support cycle times of months, if ever ...)</description>
		<content:encoded><![CDATA[<p>We wanted to make a &#8220;Packed&#8221; version of our application, mainly for demo purposes (one single EXE with all data files embedded and no &#8220;installation&#8221; required). For that we had some particular needs : our application requires various service files, whose names and locations (at runtime) depend on the actual EXE name and/or location, and therefore are not fully predictable at build time.</p>
<p>That feature (env variables in BoxedApp Packer) allowed us to answer very easily to those needs, that would have otherwise require some scripting or additional developments. Finally, we did not have to change one single bit in our original EXE. I can also testify that the BoxedApp product team has been quite efficient, with a cycle time of a few hours (well, maybe you know some software companies who have support cycle times of months, if ever &#8230;)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
