<?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: Tip of the Day &#8211; Update your copy of Flex Builder</title>
	<atom:link href="http://blog.natebeck.net/2009/01/tip-of-the-day-update-your-copy-of-flex-builder/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.natebeck.net/2009/01/tip-of-the-day-update-your-copy-of-flex-builder/</link>
	<description>AIR, Flex / Flash, FMS, PushButton, Game... Developer</description>
	<lastBuildDate>Mon, 11 Jul 2011 19:09:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: rob mckeown</title>
		<link>http://blog.natebeck.net/2009/01/tip-of-the-day-update-your-copy-of-flex-builder/comment-page-1/#comment-44</link>
		<dc:creator>rob mckeown</dc:creator>
		<pubDate>Tue, 27 Jan 2009 19:15:42 +0000</pubDate>
		<guid isPermaLink="false">http://blog.natebeck.net/?p=428#comment-44</guid>
		<description>I ran into an issue with this. After upgrading to 3.0.2, I was unable to extract the data visualization source code. When I used the instructions on Adobe&#039;s blog (http://blogs.adobe.com/flexdoc/2008/04/extracting_data_visualization.html), it told me that my license key was invalid. Even though the same license key was accepted by FlexBuilder without a problem.</description>
		<content:encoded><![CDATA[<p>I ran into an issue with this. After upgrading to 3.0.2, I was unable to extract the data visualization source code. When I used the instructions on Adobe&#8217;s blog (<a href="http://blogs.adobe.com/flexdoc/2008/04/extracting_data_visualization.html" rel="nofollow">http://blogs.adobe.com/flexdoc/2008/04/extracting_data_visualization.html</a>), it told me that my license key was invalid. Even though the same license key was accepted by FlexBuilder without a problem.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steven Erat</title>
		<link>http://blog.natebeck.net/2009/01/tip-of-the-day-update-your-copy-of-flex-builder/comment-page-1/#comment-43</link>
		<dc:creator>Steven Erat</dc:creator>
		<pubDate>Tue, 27 Jan 2009 13:49:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.natebeck.net/?p=428#comment-43</guid>
		<description>I ran into a small, related issue worth mentioning here...

I had FB Pro installed which shipped with Flex SDK 3.0.  I wanted to update it to use the latest SDK so I went to opensource.adobe.com, downloaded version 3.2 next to my existing 3.0, then added 3.2 as a new Flex compiler option.

When I went to use charting I discovered that FB couldn&#039;t find the component implementations of things like mx:PieChart.  

I later realized that the downloadable SDK is different from the SDK that shipped in FB because the opensource one does not contain the subdirectory fbpro/ which has all the charting components.

It would have been my expectation that the SDK of any specific version would always be identical, and that a license key would unlock functionality not available to those without a license (Similar to how the bits for ColdFusion Enterprise are identical to ColdFusion Standard, and your license determines the available feature set).

So, the only way to update your SDK *and* get the charting components is to update your Flex Builder to get the built-in SDK.</description>
		<content:encoded><![CDATA[<p>I ran into a small, related issue worth mentioning here&#8230;</p>
<p>I had FB Pro installed which shipped with Flex SDK 3.0.  I wanted to update it to use the latest SDK so I went to opensource.adobe.com, downloaded version 3.2 next to my existing 3.0, then added 3.2 as a new Flex compiler option.</p>
<p>When I went to use charting I discovered that FB couldn&#8217;t find the component implementations of things like mx:PieChart.  </p>
<p>I later realized that the downloadable SDK is different from the SDK that shipped in FB because the opensource one does not contain the subdirectory fbpro/ which has all the charting components.</p>
<p>It would have been my expectation that the SDK of any specific version would always be identical, and that a license key would unlock functionality not available to those without a license (Similar to how the bits for ColdFusion Enterprise are identical to ColdFusion Standard, and your license determines the available feature set).</p>
<p>So, the only way to update your SDK *and* get the charting components is to update your Flex Builder to get the built-in SDK.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Updating Flex Builder &#124; Psyked</title>
		<link>http://blog.natebeck.net/2009/01/tip-of-the-day-update-your-copy-of-flex-builder/comment-page-1/#comment-41</link>
		<dc:creator>Updating Flex Builder &#124; Psyked</dc:creator>
		<pubDate>Tue, 27 Jan 2009 08:47:24 +0000</pubDate>
		<guid isPermaLink="false">http://blog.natebeck.net/?p=428#comment-41</guid>
		<description>[...] http://blog.natebeck.net/2009/01/tip-of-the-day-update-your-copy-of-flex-builder/  Posted by James&#160;Ford [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://blog.natebeck.net/2009/01/tip-of-the-day-update-your-copy-of-flex-builder/" rel="nofollow">http://blog.natebeck.net/2009/01/tip-of-the-day-update-your-copy-of-flex-builder/</a>  Posted by James&nbsp;Ford [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

