When you deploy an application, ensure that the directory structure of the deployed application is correct.

When you deploy your application, must be aware of how your application accesses its assets. If you embedded all of your application assets into the SWF file, you can deploy the application as a stand-alone SWF file.

However, if your application accesses assets at run time, the application requests assets during execution. You must ensure that you deploy all of the necessary assets, in the correct location, so that you can run the application correctly.

Assets that you deploy at run time include:

• HTML wrapper
• Deep linking files
• Express Install files
• RSLs
• Modules
• Compiled CSS SWF files
• Resource modules (for localization)
• Images, sound files, and other binary assets that are not embedded
• Data files

In some cases, the deployed locations of these files must match the locations of the files during development. For example, if you load modules from the same directory as your main application, then you must deploy these modules to that directory, unless you programmatically handle alternative locations to load the modules from.

In other cases, the deployed locations of these files is specified. For example, the deep linking files history.css, historyFrame.html, and history.js must all reside in a /history subdirectory that is located relative to the application's SWF file.

And in other cases, you specify the eventual deployed location of these assets when you compile your application. For example, if you compiled your application using an RSL, you must ensure that the RSL is also deployed to your web server, along with your application's SWF file. The directory location of the RSL must match the directory location that you specified at compile time using the runtime-shared-libraries or runtime-shared-library-path options for the compiler.

For more information about what assets to deploy with your application, see Deployment checklist.