Genetec Inc. maintains backward compatibility for Security Center. Method and property signatures are kept the same with the release of a new version, but new methods, properties, and classes are released with new versions of the software.
For instructions on how to test your whether your integration works as expected, see backward compatibility in the Security Center SDK Developer Guide.
Exceptions to the rule
If a modification has to be done to the SDK for Security reasons, Genetec might introduce breaking changes to the SDK.
Any breaking changes are documented in the "Security Center SDK Release Notes" documents.
In case a property or method must become obsoleted, Genetec keeps the old functionality for the subsequent three versions.
For example, if something has been deprecated during the development of 5.9, Genetec ensures that this functionality continues working for at least versions 5.10, 5.11, and 5.12. However, as of version 5.13, that functionality may be removed or not properly maintained.
We recommend that you regularly consult the "Security Center SDK Release Notes" where we document obsoleted members. We also recommend that you modify the code as soon as possible if anything deprecated is used.
Integrations made in specific versions of Security Center can connect to at least 3 newer versions of Security Center. However, they cannot connect to versions previous to the one the integration was created in.
For example, an integration made with the 5.9 SDK can connect to Security Center 5.10, 5.11, and 5.12, but an integration made with 5.11 SDK can’t connect to Security Center 5.10 or an earlier version.
Best Practice: Follow the guidelines in Using backward compatibility and test in the environments you intend to work with before deploying.