having worked with the Flash Builder 4 Beta 2 for a while on a project that targets the Air 2 platform, I tried to import my Flex project into the new Flash Builder 4.
Unfortunately things seem to be handled differently compared to the beta release: Overlaying the Adobe AIR SDK for use with the Flex SDK (http://labs.adobe.com/wiki/index.php/AIR_2:Release_Notes#How_to_overlay_the_Adobe_AIR_SDK_ for_use_with_the_Flex_SDK) does not seem to work, or am I missing something?
For example, I get error messages like 'Could not resolve <mx:Canvas> to a component implementation.'. OK, I tried what FB would do when I create a new Flex project, and found that the namespace for mx components had changed from xmlns:mx="library://ns.adobe.com/flex/halo" to xmlns:mx="library://ns.adobe.com/flex/mx". But applying this change to my project didn't get me much further....
Is there a readme for people like me who just want to move from the FB 4 Beta 2 to the new FB 4 with their Air 2 projects??
Thanks to all of you in advance
I can tell you I had a lot of problems until just created a new workspace, copied the files manually and it
all worked fine for me then. Probably stuff embedded in the old .metadata
1) Make sure you project is pointing to the right SDK after you imported
2) Make sure that SDK name is in your preferences Flash Builder > Installed Flex SDKs and it points to the right location
Sounds like you're overlaying AIR 2 over SDK 4.0.0 correct? There was an issue in Beta 2 about this http://blogs.adobe.com/jasonsj/2010/02/workaround_for_using_the_latest_nightly_sdk_40_buil ds_with_flash_builder_beta_2.html. In the final relase of Flash Builder 4, you no longer need to apply this fix.
If that's not the issue, an easy way to debug is to look at the "Referenced Libraries" in Package Explorer and verify (1) the right SWCs are there and (2) you can expand the SWCs and see all the classes that should be there.
Jason San Jose
Software Engineer, Flash Builder