Changes in Extension Manager CC


Extension Manager team

Important information for anyone wishing to create products for CC

Jan 09, 2014 02:59 PST

Changes in Extension Manager CC

Various changes have been made to the extension installation configuration file specification (*.MXI) in the recent Extension Manager CC release. This release also removed some fault-tolerant processing in order simplify logic and improve performance. As a result, some extensions which can be installed successfully in CS6 may not be successfully installed in CC. In order for your products to be installed successfully in Extension Manager CC, please bear in mind the following information.

Get the complete MXI file specification for Extension Manager CC.

Summary of MXI specification changes

  • Extension Manager CC removed the fault-tolerant processing of the “destination” attribute of the “file” tag. The MXI specification has long stipulated that the value of the “destination” attribute should not include the file name, and Extension Manager CC now enforces this rule. (Extension Manager CS6 and earlier were more lenient, allowing file names to be used). For example, the following tag will cause Extension Manager CC copy sample.html to the wrong folder:
    <file source="sample.html" destination="$ExtensionSpecificEMStore/com.test/html/sample.html" />

  • Extension Manager CC no longer supports Fireworks. If “Fireworks” is specified in the “product” tag, it will be ignored.
  • The “primary” attribute in “product” tag is ignored by Extension Manager CC.
  • The “show-files”, “mxiversion” and “xmanversion” attributes in “macromedia-extension” tag are ignored by Extension Manager CC.
  • For hybrid extensions, the “file-type” attribute must be set to “CSXS” for all embedded CEP extensions. For example,
    <file source="test.zxp" destination="" file-type="CSXS" />
  • The dependency rule has been simplified. Only the extension name may now be specified for the “extension” tag under the “dependency” tag. The “version”, “minversion” and “maxversion” attributes are ignored.
  • The “prompt” and “default” attributes in “token” tag are no longer supported by Extension Manager CC.
  • Undocumented attributes are no longer supported by Extension Manager CC. For example, in Extension Manager CS6 and earlier, there existed a few attributes for which specific variant names which would also be accepted. Starting with Extension Manager CC, only documented attribute names are accepted.
  • Duplicate elements are not permitted in the “files” tag.
  • Illustrator, InDesign and InCopy have both 32-bit and 64-bit versions on Windows which have different product names. The “familyname” attribute can be used to refer to all of these. For example, if your extension should be installable on both versions of InDesign, you should specify:
    <product familyname="InDesign" version="9.0" />
    If you specify <product name="InDesign" version="9.0" />, it will only be installed for InDesign 32-bit on Windows.

Other changes

  • MXP extensions are no longer supported in Extension Manager CC. You can convert MXP extensions to ZXP extensions with Extension Manager CS6.

  • Extension Manager CC no longer supports “Package Extension” feature. Adobe Exchange Packager can be used for this purpose.

  • Extension Manager CC no longer provides option to install per-user extensions for all users. Per-user extensions are installed to a location under the user’s home folder.

  • Extension Manager CC supports installing an extension by BridgeTalk (the message body format has changed), but no longer supports enabling/disabling/removing/updating extension by BridgeTalk.

  • Extension Manager CC doesn’t support rollback of file operations. This means that if extension installation fails, some files may be left behind on the user’s machine.

  • A new command line tool is provided which no longer depends on a GUI module or AIR runtime. Note that the command line usage has changed. Run the tool without parameters to see more usage information.

  • Extension Manager CC added check for extension dependency upon extension installation. Per-machine extensions cannot depend on per-user/mixed extensions, which means that if a per-machine extension depends on a per-user/mixed extension, it cannot be installed by Extension Manager CC. Per-machine extensions are extensions whose files are installed to user-independent locations. Mixed extensions are extensions whose files will be installed to both user-independent folders and the user’s home folder.