Integrating a AIR application installer

[BillMcLean]

I'm researching how to integrate a Adobe AIR application into an existing SetupFactory for Windows 1.0 installer. This poses a number of issues that must be addressed.

Is there any example on how to add to the AIR installer to the setup bootstrap loader? The issues that need to be addressed are:

1) If the AIR runtime is not installed ensure that it is installed by the setup bootstrap loader.

2) Execute the .AIR package which installs the AIR application.

3) Finish the rest of the application.

Uninstall

1) uninstall the AIR application and not the run time


Unfortunately, I posted this to the Setup Factory 7.0 forum :wow A little bit of confusion on my part.

[Adam]

Bill,

We don't have a pre-made Adobe AIR dependency module for the bootstrapper at this time.

Almost everything that you are looking for is possible using the bootstrapper.

1,2 and 3 are the basics of what goes into every module. If you would like to make one it would be best to use one of the existing ones (.net) as a template. I will include this as an official suggestion and it may be made for a future service release.

As far as the uninstall goes this may pose a problem. In general the dependencies are not uninstalled. The MSI uninstall is quite rigid and does not leave much room for this type of functionality. It could most likely be hacked by using a custom action set to run on uninstall. This would require that you know how to launch the uninstall manually.

Hope this helps.

The reference number for the request to make Adobe AIR module is REF: 17432

Adam Kapilik

[BillMcLean]

Thanks Adam,

I will go ahead and work with a .net bootstrapper.

All AIR application installers have the .air extension. After the AIR runtime has been installed, a file with this extension can be run from the command line. Do you forsee any potential problems?


Bill

[Adam]

Sorry for the late reply. Our script has the ability to do 'shell' execution of files. If the extension is registered with Windows then it should open fine using a Shell.Execute() or File.Run() action.

Adam Kapilik