I have this problem with Flex Builder 3. If I have “Build Automatically” checked under “Project”, my workspace gets stuck in this “Building Workspace” limbo and can never launch any projects for testing unless I toggle this setting back off.
I’ve had the feature disabled for a few months now, but with the release of AIR 1.1 and the Flex 3.0.2 SDK, I decided to try and enable it again. Unfortunately, this has had no affect on this particular issue- so it must be more FB-related than SDK-related.
If anyone has any insight on this issue- I’m all ears.
Another tip is to close projects you aren’t using. When a project is closed, the resources within the project are “offline”. This should help with startup time, performance, and use less memory.
Make sure that your build process doesn’t drop anything in your source folders.
For example, setting the dump-config param in your compiler configs can cause this problem (especially if you’re compiling a SWC). If the process of compiling alters the contents of the compilation targets, a new compilation is triggered — and the circle continues.
HTH
Marty
I’ve closed all projects not in use and this has fixed the issue for me. Must be something funny in one of those. Thanks, Mike!
Great content, exactly what I had been seeking out.
Hello,
I know this blog entry is from 2008 but it refers to the same issue that I have detected on the Flash Builder 4.5 and, in this case, closing all other projects does not prevent the loop.
I’ve tried finding a solution for it but its is difficult to search in the web (I keep going to “how to build projects” and “adobe’s building feature”).
If you happen to be using Flash Builder 4.5 and have solved this can you please advice me?
Thanks in advance,
BP
yeah, I have the same problem with you.
and now, there are no any solutions searched…..