We have a compute intensive application that provides
services to the our air application. We are want to distribute both
using a single installer.
We have accomplished this by:
1) On a reference machine we install our air application
using the air installer.
2) We build our third party installer insuring that all the
files that the air installed are included as part of the .msi built
by the third party installation tool. Of course we include all
files to be installed by our compute intensive application.
We have validated this on a number of target machines and it
seems that this process seems to work correctly.
1) Is it sufficent to just replace the .swf file when code
changes occur in the AIR application? It appears to be.
2) Are there any issues that need to be addressed using this
1) You won't be able to use the encrypted local store or DRM
features. Modifying the installed .swf, etc. without re-installing
the application breaks the application's signature, and a valid
signature is required to access those features.
2) Installing the same files via two different installers
breaks the MSI component model. Among other problems, that means
uninstalling either of these two products will cause the shared
files to be prematurely uninstalled.