Skip to main content
Inspiring
June 24, 2016
Question

Is there a compatibility guide about InDesign and plug-ins compiled with diff SDK?

  • June 24, 2016
  • 3 replies
  • 538 views

I have some InDesign plug-ins for CC 2015 that compiled with SDK 2015.0(11.0), recently I found that some of them cannot be loaded by InDesign CC 2015.3. There was a message said that the plug-in should be compiled with SDK 2015.2(11.2) at least. The confusion thing is that it didn't complain for all plug-ins compiled with SDK 11.0.

Those plug-ins have issue in ID 2015.3 also cannot be loaded in 2015.4, after recompiling with SDK 11.2, they can be loaded in both version of ID.

My question is how do I know the compatibility between InDesign CC 2015 and the plug-ins compiled with its SDK. Or, is there a way to configure that?

The experience I can get from CS age is that for the same major version of InDesign, it at least can load the plug-ins compiled with lower minor version SDK in InDesign. It looks like not true for InDesign CC now, so I'm not sure how to tell the users of my plug-in what versions of InDesign are supported.

Thank you.

This topic has been closed for replies.

3 replies

Alo Lohrii
Participating Frequently
June 30, 2016

Could you please point out one example sample from 11.0 SDK which wouldn't load in InDesign 11.3? I tried the basic dialog sample which does load ok for me

Eric DWKJAuthor
Inspiring
June 30, 2016

I will try to find the related plug-in, it happened days ago.

Those plug-ins are part of our commercial product, so I'm not sure whether I can send you those things so far after we can find out the one caused the issue.

Alo Lohrii
Participating Frequently
June 29, 2016

Taking this to the product team, hoping to get more clarity, please stay tuned

vinothr
Inspiring
June 29, 2016

This is a very valid concern.

Currently, there is no straightforward lookup table wherein you can find the SDK compatibility details.

However, the SDK documentation (docs/html/index.html) has some basic information about the release history of SDK.

Moreover, there is a porting guide at API level changes.

In short, there is no explicit information about this. I think Adobe should help developers in some way to address this versioning.