Preparing add-ins for loading them to configurations





An add-in can be packed to a ZIP archive. This is mandatory if you want to use the add-in with the thin or web client or with the mobile platform.

The archive for the desktop platform must include add-ins for Windows  (x86, x86_64), GNU/Linux (x86, x86_64), extensions for Internet Explorer (x86, x86_64) and Mozilla Firefox (Windows x86, GNU/Linux x86, and x86_64).

The archive for the mobile platform must include add-ins for Windows RT (x86, ARM), Android (x86, ARM, and optional .apk file for Java code), and iOS (ARM and ARM64 combined in a single universal file). The iOS version must include both a static and a dynamic library.

The archive must also include the MANIFEST.XML file with the content description.

The archive for the mobile platform can also include the following optional files:

  • IOS_MANIFEST_EXTENSIONS.XML (for iOS). Describes the permissions to use additional frameworks.
  • ANDROID_MANIFEST_EXTENTIONS.XML (for Android). Describes the changes in AndroidManifest.xml.

  • WINDOWS_RT_MANIFEST_EXTENTIONS.XML (for Windows Runtime). Describes the changes in AppxManifest.xml.

  • WINDOWS_RT_PHONE_MANIFEST_EXTENTIONS.XML (for Windows Runtime Phone). Describes the changes in AppxManifest.xml.

In the desktop platform, add-in archives are loaded to configuration templates having "Add-in" or "Binary data" type.

In the mobile platform, add-in archives are loaded to configuration templates having "Add-in" type.


Comments
0
Add comment