| Using Flex Builder 2 > Programming Flex Applications > Running and Debugging Applications > Understanding running and debugging applications in Flex Builder | |||
|
|||
|
|||
|
|||
After your projects are built into applications (see Building Projects), you can run and debug them in Flex Builder.
A launch configuration defines such things as the project name, the main application file, the path to the run and debug versions of the application, and so on. Flex Builder contains a default Flex application launch configuration that is used to create launch configurations automatically for each of your projects. For more information, see Managing launch configurations.
|
NOTE |
|
In the plug-in configuration of Flex Builder, a launch configuration is not automatically created for you. You need to create one the first time you run your application. See Running your applications. |
You can customize the launch configurations that Flex Builder creates automatically for you. For example, you can switch the main application file or modify the path to point to the SWF file rather than the HTML wrapper file so that you can run and debug your applications directly in the Flash desktop player instead of a web browser. You can also create separate launch configurations for each of the application files in your project. For more information, see Creating or editing a launch configuration.
By default, the launch configuration specifies that the run and debug paths point to the HTML wrapper files in the output folder of your project; therefore, your applications are run and debugged in Flash Player running in a web browser. You can instead run and debug your applications in the Flash desktop player (see Running the application SWF file in the stand-alone Flash Player). You can also override the system default web browser setting and run your applications in any browser you have installed (see Changing the default web browser).
The Flex Builder Debugging perspective provides all of the debugging tools you expect from a robust, full-featured development tool. You can set and manage breakpoints; control application execution by suspending, resuming, and terminating the application; step into and over the code; watch variables; evaluate expressions; and so on. For more information about the Flex Builder debugging tools, see Debugging your applications.
You add breakpoints to executable lines of code in the code editor. When you begin a debugging session, the application runs until the first breakpoint is hit. The Debugging perspective is then activated and you can inspect the state of and manage the application by using the debugging tools. For more information, see Starting a debugging session.
If you haven't already done so, review the getting started lesson in Debug an Application in Getting Started with Flex 2. For more information, see the following sections in this topic:
Flex 2.01
