#Adobe dc vs xi install#
#Adobe dc vs xi upgrade#

WxPlugin: Upgraded to use wxWidgets 3.1.3. There is no вЂњAcrobat ReaderвЂќ specific path for 64-bit there is for 32-bit.ДЄpp Wizard: The App wizard has been upgraded and will only work with VS2019.

#Adobe dc vs xi install#

Product differentiation (Reader vs Acrobat) at install time is not possible.Д¦4-bit: /Program Files/Adobe//Acrobat/plug_insДЈ2-bit: /Program Files (x86)/Adobe//Acrobat/plug_ins Plugins need to ensure Acrobat specific HFTs are not invoked while the application is running in Reader mode.Д®xisting plugins with different binaries for Acrobat and Reader must combine into a single binary. If any Acrobat-specific HFT is invoked in Reader Mode, it could throw a run-time exception. The application can transition from Reader mode to Acrobat mode without a relaunch, so plugins must react to mode notifications accordingly.

Plugins must dynamically check the whether the app is in Acrobat or Reader mode in order to determine what functionality should be available. The unified application determines the mode in which itвЂ™s running (Reader/Acrobat) at run time.

#Adobe dc vs xi upgrade#

The SDK provides 64-bit public headers to 3rd party plug-in developers so that they can successfully create or upgrade their plugins.ДЄcrobat and Reader use the same, single installer. You must upgrade 32-bit plugins to 64-bit for them to work with the 64-bit app. While the app will continue to load existing Intel-based plugins when running under Rosetta translation, developers should migrate their plugins to the ARM architecture so they can load in the native mode of the app. In the app running natively on Apple silicon devices, plugins compiled for Intel architecture are not loaded. For existing plugins, set the architecture to $(ARCHS_STANDARD) as shown: All macOS plugins should be built using Xcode12 for supporting Apple Silicon. The SDK samples also now produce universal binaries and require Xcode12 to build. Going forward, plugins must be universal binaries so that they can work seamlessly with both Intel and Apple silicon mode. Although the apps compiled for Intel work on the Apple silicon devices with the help of Rosetta translation, there is a performance degradation. The Apple silicon chip is based on an ARM architecture which requires app and plugin migration. Because Apple is releasing new devices with their own chip instead of IntelвЂ™s, the SDK now supports native Apple Silicon mode for third party plugins.