This content has been marked as final. Show 5 replies
With AIR apps, if you have an instance of the app running. not in debug mode, then it seems like you can't debug the app till you close that open instance. Maybe that's it.
thanks for your quick reply
I haven't got any other instances of the application running at all, and the issues still there. I was able to just get debug working again, but now it's stopped compiling once more, and so it's time for PC restart #8 of the day.
Please can someone help?
"Mattg2379" <email@example.com> wrote in message
> Hi all.
> I've had this problem on and off for a few weeks, but today it's been
> I'm using build 3.01.205647 of Flex Builder.
> When I try to compile an AIR app locally to test, it's throwing an error
> (#2030, which I'm fixing)
> However, the trouble I'm having is that whenever I fix the issue and try
> recompile, nothing happens. The workspace is refreshed by the builder, but
> nothing else.
> I also have almost constant trouble with using the Flex debugger. It never
> wants to run, and says:
Process terminated without establishing connection to debugger.
> Command: "C:\Program Files\Adobe\Flex Builder 3\sdks\3.1.0\bin\adl.exe"
> C:\Inetpub\wwwroot\BTX-debug\BTX_4-app.xml C:\Inetpub\wwwroot\BTX-debug
> Output from command: invocation forwarded to primary instance
> Please can someone help me? I'v restarted my pc five times today, and have
> do so each time Flex Builder freezes up.
Did you try Project>clean?
It seems to me AIR projects have more problems getting "dirty" than others.
You may also find this link helpful
I wonder if an AIR related process is still running, though not visible. Is this Windows? Is there an adl.exe in TaskManager?
I found that killing the ADL process solved the problem for me.