That is definitely not a bug in 3.5a. I have been using 3.5 for the past week without any such issues. But I have been having this problem on and off for around 3 years since flex builder 2. As far as I can recall, recreating your workspace in different location might be helpful since FB does a lot of caching in the workspace folders which might interfere with your sdk upgrade.
On Mon, Feb 22, 2010 at 8:08 AM, mitek17 <mite...@gmail.com> wrote: > > > Seems like Adobe screwed up namespaces in 3.5 > > Here is the bug I filed in regards to DesignView not understanding mx > namespace for components. > https://bugs.adobe.com/jira/browse/FB-25994 > > I wonder if *anyone* uses 3.5 SDK. I did 3 attempts to migrate from 3.4 and > they all failed. > > PS Probably Adobe needs more spanking from Steve Jobs :) > > Cheers, > Dmitri. > > > --- In flexcoders@yahoogroups.com <flexcoders%40yahoogroups.com>, > "mcaplan_labnet" <mcap...@...> wrote: > > > > Hi There, > > > > I'm unsure what is going on, but I can't compile my project under 3.5. > Works fine under 3.4. I get the following errors in 3.5: > > > > Encountered errors or warnings while building project Alloys.mxml. > > Alloys.mxml: Invalid component name 'modules.Alloys': component name must > be legal ActionScript class name. > > Encountered errors or warnings while building project Case.mxml. > > Case.mxml: Invalid component name 'modules.Case': component name must be > legal ActionScript class name. > > > > > > Any ideas? > > > > Thanks, > > > > Mike > > > > >
