<?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: Thinking About Google Chrome Frame Deployment</title>
	<atom:link href="http://accidentaltechnologist.com/technology/thinking-about-google-chrome-frame-deployment/feed/" rel="self" type="application/rss+xml" />
	<link>http://accidentaltechnologist.com/technology/thinking-about-google-chrome-frame-deployment/</link>
	<description>Musings about Technology, Software Design and Development</description>
	<lastBuildDate>Sun, 22 Jan 2012 21:23:06 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Alex Russell</title>
		<link>http://accidentaltechnologist.com/technology/thinking-about-google-chrome-frame-deployment/#comment-2170</link>
		<dc:creator>Alex Russell</dc:creator>
		<pubDate>Wed, 22 Sep 2010 18:49:00 +0000</pubDate>
		<guid isPermaLink="false">http://localhost/~rbazinet/?p=374#comment-2170</guid>
		<description>This post is the first Google result for &quot;Chrome Frame MSI&quot;, so I figure I should mention here that MSI packages are available for GCF, including for the new Stable version:

http://www.google.com/chromeframe/eula.html?msi=true

Using Omaha policy templates, you can also control the update process:

http://code.google.com/p/omaha/wiki/UpdateControls

Regards</description>
		<content:encoded><![CDATA[<p>This post is the first Google result for &#8220;Chrome Frame MSI&#8221;, so I figure I should mention here that MSI packages are available for GCF, including for the new Stable version:</p>
<p><a href="http://www.google.com/chromeframe/eula.html?msi=true" rel="nofollow">http://www.google.com/chromeframe/eula.html?msi=true</a></p>
<p>Using Omaha policy templates, you can also control the update process:</p>
<p><a href="http://code.google.com/p/omaha/wiki/UpdateControls" rel="nofollow">http://code.google.com/p/omaha/wiki/UpdateControls</a></p>
<p>Regards</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JasonFree</title>
		<link>http://accidentaltechnologist.com/technology/thinking-about-google-chrome-frame-deployment/#comment-914</link>
		<dc:creator>JasonFree</dc:creator>
		<pubDate>Fri, 09 Oct 2009 08:39:23 +0000</pubDate>
		<guid isPermaLink="false">http://localhost/~rbazinet/?p=374#comment-914</guid>
		<description>&lt;p&gt;The Chrome Frame setup could be very useful...but corporations DEPLOY their software using remote install mechanisms. Those mechanisms vary, but the simple matter of the lack of an MSI with the usual documentation and install options will prevent many users in the corporate world from seeing this add-on.&lt;/p&gt;
&lt;p&gt;We won&#039;t be running out and manually installing this one 20&#039;000 desktops. It just won&#039;t get installed unless we have it packaged.&lt;/p&gt;
&lt;p&gt;JB&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>The Chrome Frame setup could be very useful&#8230;but corporations DEPLOY their software using remote install mechanisms. Those mechanisms vary, but the simple matter of the lack of an MSI with the usual documentation and install options will prevent many users in the corporate world from seeing this add-on.</p>
<p>We won&#8217;t be running out and manually installing this one 20&#8217;000 desktops. It just won&#8217;t get installed unless we have it packaged.</p>
<p>JB</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JasonFree</title>
		<link>http://accidentaltechnologist.com/technology/thinking-about-google-chrome-frame-deployment/#comment-2011</link>
		<dc:creator>JasonFree</dc:creator>
		<pubDate>Fri, 09 Oct 2009 08:39:00 +0000</pubDate>
		<guid isPermaLink="false">http://localhost/~rbazinet/?p=374#comment-2011</guid>
		<description>The Chrome Frame setup could be very useful...but corporations DEPLOY their software using remote install mechanisms. Those mechanisms vary, but the simple matter of the lack of an MSI with the usual documentation and install options will prevent many users in the corporate world from seeing this add-on.
We won&#039;t be running out and manually installing this one 20&#039;000 desktops. It just won&#039;t get installed unless we have it packaged.
JB</description>
		<content:encoded><![CDATA[<p>The Chrome Frame setup could be very useful&#8230;but corporations DEPLOY their software using remote install mechanisms. Those mechanisms vary, but the simple matter of the lack of an MSI with the usual documentation and install options will prevent many users in the corporate world from seeing this add-on.<br />
We won&#8217;t be running out and manually installing this one 20&#8217;000 desktops. It just won&#8217;t get installed unless we have it packaged.<br />
JB</p>
]]></content:encoded>
	</item>
</channel>
</rss>

