Kalen Gibbons

I’ll be presenting at the IECFUG this Thursday the 9th. The session will be a hands-on tutorial on connecting ColdFusion and Flex. It should be a good time, so come on down if you’re in the area.

I’ll post the sample files here sometime after the meeting.
It’s a little late, but here are the links to the files and the presentation, enjoy
Presentation Files
Presentation on Adobe Connect

Note: An update to this topic has been posted here. It provides a better solution than the one offered below, so I recommend you check it out before continuing.

Have you ever had a Flex application that worked fine in your development environment but not when you moved it to your production server? How do you debug the problem?

You can use the following trick to enable Flex Builder to establish a debug connection to a remote server.

1. First, compile a debug version of the application and deploy it to your remote server.
2. Then go into the project’s properties in Flex Builder (Project >> Properties >> Flex Build Path) and change the “Output folder URL” to an invalid URL (this can be almost anything).
   
   
3. Compile your application again in debug mode. This time, Flex Builder will launch the invalid url and will not be able to connect to the debugger.
   
   
4. While Flex Builder is waiting to connect to the debugger, navigate to the debug SWF that you put on your remote server. Don’t forget to include ?debug=true in the querystring.
5. Flex Builder will connect to the remote swf the same way it would have connected to your local version. You can use breakpoints, inspect variables, and do everything you could do locally.
   
   

This trick comes in really handy when you have problem related to a specific environment. I hope this can help ease the pains of debugging for some of you.