You can export an optimized release-quality version (non-debug SWF or AIR file) of your application using the Export Release Build Wizard. Required assets are copied to a folder separate from the debug version with or without source code ("View Source" in the application context menu). A .zip archive is also created automatically. You access the wizard from the Project menu or on the toolbar.

Export Adobe AIR application installer

For AIR projects, a production build creates a digitally signed AIR file, which the user must install before running the application. This process is similar to creating an installer .exe for a typical native application. Optionally you can create an unsigned intermediate package which you can sign later before release. Before you begin the Export Release Build, you must decide how to digitally sign your AIR application:

• Sign the application using a VeriSign or Thawte digital certificate
• Create and use a self-signed digital certificate
• Choose to package the application and sign it later

Digital certificates provided by VeriSign and Thawte give users some assurance as to your identity as a publisher and verification that the installation file has not been altered since you signed it. Self-signed digital certificates serve the same purpose but they are not validated by a third-party.

You also have the option of packaging your AIR application without a digital signature by creating an intermediate AIR file (.airi). An intermediate AIR file is not valid in that it cannot be installed. It is instead used for testing (by the developer) and can be launched using the AIR ADT command line tool. This capability is provided because in some development environments signing is handled by a particular developer or team, which ensures an additional level of security.

1. Select Project > Export Release Build.
2. In the Export Release Build wizard, choose the export settings for project, application, and folder.
   • If your project does not have a server web root associated with it, all assets are copied to the project_name folder, which is the default location.
   • If your project has server web root associated with it (for example, PHP and J2EE), all assets are copied to the web_root/project_name-debug folder.
   • If you want users to view source code, select Enable View Source.
   • Click Choose Source Files to select files to you want to publish, then click OK.
   • Click Finish.

For more information about Adobe AIR files, see the Adobe AIR Developer's Guide.

Digitally signing your AIR applications

1. Select Project > Export Release Build.

   If you have multiple projects and applications open in Flex Builder, select the AIR project you want to package.

2. (Optional) Select Enable View Source if you want users to see the source code when they run the application.

   Click Choose Source Files to select individual files (all source files are selected by default).

3. On the Digital Signature page:

   Specify the digital certificate that represents the application publisher's identity. To generate a self-signed certificate, click Create to enter data in required fields.

   If you want to export a file that will be signed later, you can export an intermediate AIRI file.

4. Click Finish.

Debug version

The debug version of your application contains debugging information and is used when you debug your application. The Export Release Build version does not include the additional debugging information and is therefore smaller in size than the debug version. An HTML wrapper file contains a link to the application SWF file and is used to run or debug your application in a web browser.

In a standard Flex application, a typical output folder resembles the following example:

You can run or debug your Flex and ActionScript applications either in a web browser or in the stand-alone Flash Player. You control how your applications are run or debugged by modifying the project's launch configuration (see Running your applications). For more information about running and debugging your applications, see Running and Debugging Applications.

When you use LiveCycle Data Services ES you create Flex applications that leverage the Flex server technologies. When building LiveCycle Data Services ES applications, you have the option of compiling the output files locally using Flex Builder or on the server when the application is first accessed.