Updating adobe online components from adobe.com

After an Initial AIR 20 installation from a Side Car, launching the package results in Mac OS X “blessing” the Adobe AIR Installer that sits next to it.Hence forward, Mac OS X remembers this application as the default launcher for an package.So the app’s launcher code will now be a 64-bit binary.The previously used 32-bit launcher gets renamed with a ‘_32’ suffix.But there are certain points, which require attention when attempting to downgrade.After you install AIR 20, any previously installed AIR app using the Shared Runtime that is launched gets updated.Benefits include greater control, the ability to create custom packages, and the ability to select install options that may not be available to users when installing apps directly.It is also possible to leverage Creative Cloud Packager to just initially download the applications and deploy to your systems; this means each machine is not downloading the same bits multiple times, congesting your network.

Companies with locked down IT environments will want to use Creative Cloud Packager.In this scenario, you can package updates via Creative Cloud Packager and hence have control over the distribution of updates. Adobe is offering customers a choice when it comes to deploying Creative Cloud.You can either deploy centrally across your organization using Creative Cloud Packager, or allow your users to download the software on their own using the Creative Cloud app for desktop.By Eric Simenel This tech note addresses the problems that you may face when attempting to downgrade from AIR version 20 to an older AIR version.Prior to AIR version 20, AIR was provided as a 32-bit Runtime dynamic Library for Mac OS X.

Leave a Reply