Upgrade AIR from Beta 1 to Beta 2

As most of you reading this probably know, Adobe AIR Beta 2 was released on the first day of the Adobe MAX conference. With the public release of Beta 2, I was able to migrate an application and deliver it to the client.

Here are a few things I discovered during the migration:

• Read the release notes twice. Read them once before you start the migration, and then keep them handy as you try to migrate. A bunch of my issues were addressed there, I just forgot about that they were listed. I forgot to Migrate the Application Descriptor.
• Flex Builder 3 includes the AIR SDK. You do not need to download and do a separate install. I would expect this to be documented somewhere, but I couldn't find it and it was a source of confusion for me.
• Keep Imports Organized went from off to on. This caused problems as I was trying to debug some code, and Flex Builder automatically started removing imported classes that were listed in the import list. As I uncommented code to isolate a bug, I got errors because the class imports were missing. You can turn this off by windows--> Properties --> Flex --> Editors --> ActionScript Code --> Keep imports organized.
• Supposedly you can run the SDK of AIR Beta 1 and AIR Beta 2 side by side, but I couldn't find any documentation on this. I backed up my Eclipse directory, then installed the Flex Builder Beta 2 plugin into "Flex Builder 3 Plug-in B2" instead of "Flex Builder 3 Plug-in". So, beta 2 went into the "B2" Directory and beta one was untouched. I upgraded my 'original' eclipse install folder. I just need to make shortcuts to each eclipse install. The backup for beta 1 usage, and the current directory for the Beta 2 usage. I would have thought the multiple SDK feature of Flex Builder would have handled his, but it didn't for me.
• When using the file APIs, the 'get file path from URL' method changed from "resolve" to "resolvePath". This is the element I remembered from the first time I read the release notes.
• And finally, I noticed that the invoke event of an AIR app was now firing before CreationComplete event instead of after. In Beta 1, I set values in creationComplete and accessed them in the invoke. In beta 2, those values were still in their default state. I had to move around some initialization code. So far as I know, this is not documented anywhere.