To create a captive runtime bundle for Windows, you must
package the application while running under the Windows operating
system. Package the application using the ADT bundle target:
-keystore ..\cert.p12 -storetype pkcs12
myApp.swf icons resources
This command creates the bundle in a directory named, myApp.
The directory contains the files for your application as well as
the runtime files. You can run the program directly from the folder.
However, to create a program menu entry, register file types, or
URI scheme handlers, you must create an installer program that sets
the requisite registry entries. The AIR SDK does not include tools
for creating such installers, but several third-party options are
available, including both commercial and free, open-source installer
You can sign the native executable on WIndows, by specifying
a second set of signing options after the -target bundle entry
on the command line. These signing options identify the private
key and associated certificate to use when applying the native Windows
signature. (An AIR code signing certificate can typically be used.)
Only the primary executable is signed. Any additional executables
packaged with your application are not signed by this process.
File type association
To associate your
application with public or custom file types on Windows, your installer
program must set the appropriate registry entries. The file types
should be listed in the fileTypes element of the application descriptor
file as well.
For more information about Windows file types,
see MSDN Library: File Types and File Associations
URI handler registration
In order for
your application to handle the launch of a URL using a given URI scheme,
your installer must set the requisite registry entries.
more information about registering an application to handle a URI
scheme, see MSDN Library: Registering an Application
to a URL Protocol