« Your First AIR 2.0 EXE file | Main | AIR 2.0 Native Installer Concerns »
Updating AIR 2.0 Flex 4 Apps
| By Rich Tretola | November 17, 2009 | |
| 13,045 views |

Just a brief FYI that may save you some pain and avoid the TypeError: Error #1007: . If you are now creating AIR 2.0 using MX / Spark, you will need to change the swc you are using for the UI from applicationupdater_ui.swc to a specific one for Flex 4 called applicationupdater_ui4.swc. If you have not been creating your AIR applications with updater capabilities, you should be.
You can get this new swc within AIR20SDK/frameworks/libs/air/flex4
For more information on updating AIR applications, please see this post.
Topics: Adobe AIR, Flex, Flex 4 | 7 Comments »









November 17th, 2009 at 1:46 pm
[...] This post was mentioned on Twitter by Rich Tretola and CT, Michael Borbor. Michael Borbor said: RT @richtretola Blogged: Updating AIR 2.0 Flex 4 Apps http://bit.ly/4uTHwA [...]
December 23rd, 2009 at 2:45 am
Coach Satchel Authentic Coach satchel purses have good quality with cheap price, shipped with original packages.
Reply to this comment
December 23rd, 2009 at 10:43 pm
discount Mbt shoes wholesale,Which one do you like best? Mbt m walk shoes or Mbt Lami?
http://www.discountmbt.com/
Reply to this comment
December 30th, 2009 at 10:23 pm
Mbt shoes are so amazing. You will have a brand new walk experience when putting on Mbt m walk, Mbt Chapa and the like
Reply to this comment
March 30th, 2010 at 5:01 am
welcome to buy wedding dresses
Free shipping, fashion style. cheaper price
http://www.wedding-dresses-mall.com
Reply to this comment
April 1st, 2010 at 2:21 am
welcome to choose the bested hardy swimsuit ,high quality,free shipping,various styles.
http://www.brand-clothing.com/ed-hardy-swimsuit-wholesale-1316_1380.html
Reply to this comment
October 29th, 2010 at 11:47 pm
You you could edit the webpage name title Updating AIR 2.0 Flex 4 Apps | EverythingFlex: Flex & AIR to more generic for your blog post you write. I loved the the writing all the same.
Reply to this comment