Air installer with runtime embedded

Hi there,

I'm investigating if/how we can use this product for our needs.We're developing for Air 2.6, and we're using the official Adobe Installer to embed a runtime, and then install the .air application.

Reading some instructions I found that to incorporate Turbo Activate I will need to create a native build for my app (exe/dmg/rpm) that runs Native Process, rather than exporting to .air.

However the Adobe Installer won't allow to install native builds, just an .air. See: http://forums.adobe.com/message/4100206

Do you know if there's a workaround for this? I need to use Air 2.6 and keep the embedded runtime option for my client.

Thanks,Jones

Hey Jones,

Reading some instructions I found that to incorporate Turbo Activate I will need to create a native build for my app (exe/dmg/rpm) that runs Native Process, rather than exporting to .air.

That's correct. The current version of our TurboActivate / Adobe AIR integration requires the native installer due to limitations in the Adobe AIR design. It is really unavoidable.

In the near future we're adding the ability for non-native installer distribution for Adobe AIR 3.0+ (see: AIR 3.0 = LimeLM for AIR (not native) apps?).

Do you know if there's a workaround for this?

You can always wrap their native installer with your own native installer. That is, you include the *.app file with their native installer output. Does that make sense?

Or you can use Adobe AIR 3.x and use the new Adobe AIR extension behavior.

> > You can always wrap their native installer with your own native installer. That is,> you include the *.app file with their native installer output. Does that make sense?> > Or you can use Adobe AIR 3.x and use the new Adobe> AIR extension behavior.

Hi Wyatt,

Thanks for taking time to reply.Actually I must stick to Air 2.x to keep compatibility with old computers. So I'm exploring the other possibility that you mentioned: "wrap their native installer with my own installer". Can you point me to a link to explore this, and see if I can avoid the problem of the native builds?

Thanks,Jones

The Using TurboActivate with Adobe AIR article is a good place to start. This explain everything you need to know to integrate TurboActivate with your app and to package it for native installers on Windows, Mac, and Linux.

Now that you have these native installers that will install most of your application, you can "wrap" this native installer in another installer that will include everything else you want to install. That is, your "wrapper" installer will include files that Adobe's crummy native installer refuses to install.

For instance, on Windows when you finish the Using TurboActivate with Adobe AIR article you'll have an Setup.exe with your app and the proper TurboActivate dependencies. Now you can use another installer creator (like NSIS or Inno Setup) to include both the Setup.exe you generated and any other files Adobe's native installer fails to include for you.

So your custom setup with do 2 things. It will install your main Adobe AIR app and it will install any additional files you have.

And you can do similar things with Linux and Mac.

Does this help clarify things?

Reply
Discard post