Aaron, you can fix this by installing the new beta of the Flash player
that came with the beta of Flex Builder.
Here is a very long explanation, copied (and edited) from a post I
just made on the Adobe forums:
I wanted to clarify a couple of things about how this new model
(creating a single debug swf, then exporting a release one later) works.
1. If you install the (beta) Flash player that came with this Flex
Builder beta, then you will NOT see the "Where is the debugger"
dialog. The Flash Player and Flex Builder changes go hand-in-hand.
Certainly I agree that with the Flash player's old behavior, having
Flex Builder create only a debug swf would cause lots of problems;
that's why we changed both. This means there will be a transition
period during which some developers will have the old debugger-player
installed, so they will see this message; that's unfortunate, but it
won't last too long. But customers will never see it, because...
2. Your customers will NOT need to upgrade their Flash player, because
the "release" version of the Flash player -- the one that all your
customers have -- never asks "Where is the debugger." The old version
didn't, and neither will the next one.
To summarize: The only scenario where this is a problem is if you run
(not debug) a debug swf in an older version of the debug player. It is
not a problem for people who have the release player (almost all
customers); it is not a problem for machines on which Flex Builder was
installed with the default options, which includes installing the new
debug Flash player.
Some of the reasons we made this change:
- Performance: It always helps to only have to link one swf instead of
two during the edit/compile/debug cycle.
- Filenames: There are several cases where the filename of the swf is
important; with the new way, the filename of the swf is always the
same. For example, if you are using modules, then you have to write this:
<mx:ModuleLoader url="MyModule.swf" />
But with the old model, you would have to write this during development:
<mx:ModuleLoader url="MyModule-debug.swf" />
... and then change it before deployment. Yuck. So then people started
using binding to work around this:
<mx:ModuleLoader url="{mungeFilename('MyModule-debug.swf')}" />
where mungeFilename() tries to figure out the correct filename. A
little less horrible than having the modify the filename before
deployment, but still not pretty.
I'm interested to hear what you think, and whether you think changes
are still required even despite the above explanation. Thanks for
trying the beta, we appreciate the feedback!
- Mike Morearty, Adobe Flex Builder team
--- In [email protected], "aaron smith"
<[EMAIL PROTECTED]> wrote:
>
> Sorry I'm not following you. Explain it to me again? Thanks.
>
>
>
> On 10/4/07, Sheriff <[EMAIL PROTECTED]> wrote:
> >
> > cause to speed up the compiling it only does debug untill you
want to
> > export then click project then export release version. So use
debug to run
> >
> > ----- Original Message ----
> > From: aaron smith <[EMAIL PROTECTED]>
> > To: [email protected]
> > Sent: Thursday, October 4, 2007 3:36:24 PM
> > Subject: [flexcoders] flex builder 3 beta 2 always launching my
app with
> > debug player.
> >
> > Why is flex buildfe 3 beta 2 always launching my app with the debug
> > player. I press the "Run" button, and I'm constantly prompted with the
> > "connect to debugger" popup. Any ideas?
> >
> >
> > ------------------------------
> > Need a vacation? Get great deals to amazing places
> >
<http://us.rd.yahoo.com/evt=48256/*http://travel.yahoo.com/;_ylc=X3oDMTFhN2hucjlpBF9TAzk3NDA3NTg5BHBvcwM1BHNlYwNncm91cHMEc2xrA2VtYWlsLW5jbQ-->on
> > Yahoo! Travel.
> >
> >
> >
>
