Release Notes for Packaging for Creative Cloud


Extension Manager team

MXI changes for Extension Manager CC

Nov 22, 2013 08:41 PST

In the Creative Cloud release, there have been some changes to the syntax of the MXI configuration file that Extension Manager CC uses to install extensions into host applications. You may find that an extension which can be installed successfully in a CS6 application does not install properly in the CC version. If this occurs, check these changes to see whether you can update it for CC.

This list summarizes the changes. For complete syntax details, see the MXI specification.

Syntax changes

  • The destination attribute of the file tag must NOT include the file name. This has always been the expected syntax, but it is now enforced. If the file name was incorrectly included in the CS6 version, the extension is installed in the wrong folder in the CC version. For example, this destination value in the file tag causes the file sample.html to be installed in the wrong folder: destination=“$ExtensionSpecificEMStore/com.test/html/sample.html”
  • For hybrid extensions, the file-type attribute must be set to CSXS for all embedded CEP extensions. For example:
  • 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. Use the familyname attribute to refer to all of these. For example, if your extension should be installable on both versions of InDesign, specify familyname=“InDesign” version=“9.0” in the product tag. If you specify name=“InDesign” version=“9.0”, the extension is installed only in 32-bit Windows.

Dependency changes

  • Extension Manager CC checks for extension dependencies upon installation. Per-machine extensions cannot depend on per-user/mixed extensions, so an extension with such a dependency cannot be installed in CC.
    • Per-machine extensions have files installed to user-independent locations.
    • Mixed extensions have files installed to both user-independent folders and the user’s home folder.
  • The dependency rule no longer accepts versions. An extension tag in the dependency section must specify only the extension name, with no version information.

Command-line changes

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

Feature no longer supported

Extension Manager CC no longer supports these features:

  • Fireworks in no longer available as a host application.
  • MXP extensions are no longer accepted. You can convert MXP extensions to ZXP extensions with Extension Manager CS6.
  • The “Package Extension” feature is not available. Use Adobe Exchange Packager can be used for this purpose.
  • The option to install per-user extensions for all users is not available. Per-user extensions are installed to a location under the user’s home folder.
  • Rollback of file operations is not available. This means that if extension installation fails, some files may be left behind on the user’s machine.
  • You cannot enable/disable or remove extensions through the BridgeTalk communication protocol. You can still install extensions through BridgeTalk, but the message body format has changed.
  • In the product tag, the primary attribute is ignored.
  • In the macromedia-extension tag, the attributes show-files, mxiversion and xmanversion are ignored.
  • In the token tag, the prompt and default attributes are ignored.
  • Undocumented attributes are no longer supported.