Well, I simply changed <mx:Script> to <fx:Script> and now it appears to be working...
Weird thing is, I did *not* change anything in all of the modules that I use with this AIR app, and suddenly they compile now, too. I only changed the Script tag in the main app... Very weird... L. On Tue, Mar 5, 2013 at 5:16 PM, Laurence MacNeill <[email protected]>wrote: > I just want to know why all of a sudden this is a problem? Never gave me > one iota of trouble in Flash Builder 4.6. I targeted the Flex 4.6 SDK in > Flash Builder 4.6 with no problems. Now, suddenly, it's a problem. > > L. > > > > On Tue, Mar 5, 2013 at 5:11 PM, Scott Talsma <[email protected]> wrote: > >> I think you might be mixing your SDKs. Here are my namespaces for a SDK >> 4.6 app, using spark: >> xmlns:fx="http://ns.adobe.com/mxml/2009" >> xmlns:mx="library://ns.adobe.com/flex/mx" >> xmlns:s="library://ns.adobe.com/flex/spark" >> >> But if your app goes back to Flex Builder 3, then you may be targeting an >> older SDK (e.g. 3.x). I would check to make sure that you are still >> compiling against the same SDK that you were using previously. >> >> Scott >> >> >> On Tue, Mar 5, 2013 at 4:49 PM, Laurence MacNeill <[email protected] >> > wrote: >> >>> So I have an AIR app that's been around quite awhile, going back to Flex >>> Builder 3 and AIR 2.x... >>> >>> I've recently upgraded to Flash Builder 4.7 and I had no troubles with >>> this app until today when I tried to run it in Debug mode -- I got some >>> errors about namespace, did a Google search, found out that I needed to >>> overlay the AIR SDK onto the Flex SDK ( >>> http://helpx.adobe.com/x-productkb/multi/how-overlay-air-sdk-flex-sdk. >>> html) and I followed those instructions... >>> >>> Then when I re-loaded Flash Builder 4.7, I started getting stuff like >>> "Could not resolve <mx:Module> to a component implementation." So more >>> Google searches, and I found out I needed to change the name-space from >>> xmlns:mx="http://www.adobe.com/2006/mxml" to xmlns:mx="library:// >>> ns.adobe.com/flex/mx". So fine, I did that... >>> >>> Now I'm getting "Unable to resolve MXML language version. Please specify >>> the language namespace on the root document tag." Can't find anything on >>> this on Google -- well, nothing that works at any rate... Found someone >>> suggesting I add the fx: namespace, so I did: >>> xmlns:fx="http://ns.adobe.com/mxml/2009" >>> >>> >>> But when I add that namespace, I get "Cannot resolve <mx:Script> to a >>> component implementation." >>> >>> WHAT IS GOING ON HERE?! I just want to debug my AIR app like I used to >>> be able to in Flash Builder 4.6. HELP! >>> >>> Thanks, >>> L. >>> >>> >> >
