Can anyone answer this?
If you want to target 10.2 and 10.3 you should download the playerglobal.swc for both version from the net and configure it on your adobe cs5 folder. Then you will get the list of players possible to target from flash in the publish settings. For AIR 2.7 you should have flash cs5.5.
Thanks for the reply.
After alot of messing around I managed to get Flash professional to have 10.3 as a target, and also managed to get a 10.3 version of the debugger to run when you select Debug Movie(Running Test Movie, which is what I usually do, still uses the original 10.1 player, and I can't find out how to update it). I'm not sure if it's buggy or I've done it wrong, because when targeting it to 10.3 and running my application through the 10.3 debugger, I seem to be loosing frame labels in some of my movie clips, getting an error:
ArgumentError: Error #2109: Frame label off not found in scene off
This is odd, because
a) I don't get said error when running with Test Movie which uses a 10.1 version of the player, and I never had it before with other versions. The symbol triggering the error clearly has a frame labeled off
b) There is no scene off in my project, I only have one scene which was the default, and it's called Scene 1.
Doing some traces, it turns out that the object is not having it's frame labels read in the 10.3 player, which is very odd and indicates to me some kind of bug or incorrect installation, but since I get the exact same error running it under the 10.3 projector, I'm inclined to think bug .
With regards to AIR 2.7, why do we need CS5.5 to use it?
I'm sorry, even you can have the AIR 2.7 with flash cs5 . Now only I tested with AIR 2.7-flash CS5 and the adt command line is working fine. I published the IPA.
When you say you got AIR 2.7 working at the adt command line with cs5, does that mean you need to use the command line to get it working? I tried getting it in CS5 and publishing an application through the softwares publish feature, but it didn't work - it flashed the publishing boxes then simply stopped and no files were generated. I must confess I've largely ignored using the command line in preference of the softwares options, but if it's required to get later versions of AIR working I'll need to look into it even if it does significantly alter my workflow. At any rate, thank you for your responses.