About backward compatibility of the framework

[sesa194123_brid]

Hi

    Where I could find the backward compatibility info of the Smart Connector framework?

    By backward compatibility, I mean, plugin developed in old version of SC framework could work on new platform without recompiling.

    It is better to provide this info in release notes so developer know whether they needs to recompile their plugin to support a new SC version.

    Thanks.

[Mike_Bielby]

Am I right in assuming that when you say be backward compatible you mean with EWS or do you mean EBO

In all cases we try to be Backward compatible and test Smart Connector Framework with each new version of EBO. We actually test every EWS enabled product from SE every time we get another version of EBO.  If we find issues that make backward compatibility an issue we report back to the R&D team and hold for a fix. If it is with the Smart Connector we fix directly.  Does this help?

[Mike_Bielby]

I also found another person asking the same question and you can see you have the same answer from myself and Jeff.

SmartConnector and EBO 2.0

[Adam_Summers · Accepted solution]

I think this question relates to compatibility of extensions. As far as I’m aware you need to match up the exact SC runtime version for that which the extension was built. This does cause some maintenance pain as an extension developer and it would be useful in future if there could be improved support for previous versions of the assemblies.

[JeffBowman]

Hi Peng,

At the moment it is as Adam Summers​ mentioned, you need to match up the exact SC run-time version for which that extension was built.

There are plans to make it more backwards compatible in a future version, so look out for that!

Regards,

-Jeff

[sesa194123_brid]

Hi Michael,

   I mean the compatibility of extensions rather than SBO.

  Thx

[sesa194123_brid]

Got it, thanks for the info, Adam and Jeff.