[Q] CEP 7 to CEP 8 transition

Hi all,

I think there is not good answer because Adobe seems not guarantee the compatibility.

But the CEP 8 code is already posted, so we can figure out.

CEP-Resources/CEP_8.x at master · Adobe-CEP/CEP-Resources · GitHub

Here's some finding from my research. (I did not know before posting question)

* CEP engine was installed with each Adobe application and it's version.

   Version info: ex)  C:\Program Files\Adobe\Adobe Illustrator CC 2017\Support Files\Contents\Windows\CEPHtmlEngine

VersionInfo.xml

   As I checked it seems update for quarterly update on CC 2017.

* Code signing file may be changed by CEP version. (CEP 8 is not posted)

   CEP-Resources/ZXPSignCMD at master · Adobe-CEP/CEP-Resources · GitHub

I think we cannot specify CEP version from minimum version only (maximum version seems not supported).

By this, I think it could be limitation as following.

a) ABC2017 plugin specify min version = 2017

    CC App 2017 will load this.

    CC App 2018 will load this.

b) ABC2018 plugin specify min version = 2018

    CC App 2017 will not load this.

    CC App 2018 will load this.

I think there is no way to support a) case to be loaded by only CC App 2017.

As CC apps are subscription base, it might be not issue though.

Thank you,

Naoki

Hi Naoki,

I try to test some extensions that made for CEP 7 and worked fine in CEP 8(some extensions using node.js).

However, I'm not shure if plugins previous version will work in new PS.

Ten

You can Install all PS versions from CC 2017, 2015.5, 2015, 2014 up to CS6 a check how it works in backward compatibility.

Most common thing is change supported PS version in manifest and add debug key in registry for new CEP version.

And older PS versions should have older Chromium version and older DevTool version.