Trados Studio API changes

This release of Trados Studio improves public APIs for easier, more robust third-party interactions. If you are a third-party developer, make sure to check the API release highlights below and the full list of API changes in the Trados Studio API release notes.

New REST API endpoints for GroupShare projects

With the Trados GroupShare 2020 SR1 CU9 release, all API endpoints have been updated from the legacy WCF (Windows Communication Foundation) to the REST protocol.

When using Trados Studio 2022 SR1 with this Trados GroupShare release, all communication is performed via the new REST API endpoints. When using Trados Studio 2022 SR1 with older Trados GroupShare versions, the communication will continue to be performed using WCF. You can check the list of new endpoints in the Cumulative Updates for Trados GroupShare 2020 SR1 article .

Assemblies retargeted to .NET Standard

Some of the available APIs have been retargeted from .NET Framework 4.8 to .NET Standard for better compatibility options and richer overall support.

Access to Studio's custom language registry

You can now access Trados Studio's custom language registry, which offers finer control over language management than the language registry provided by Microsoft.

General API changes

Plugins designed for earlier versions of Trados Studio might not work with Trados Studio 2022 SR1 due to several updates to the API and infrastructure in this release. The addition of the 'RequiredProduct' setting in the Plugin Manifest now allows the RWS AppStore to accurately identify plugins that are compatible with this Trados Studio version. For further details, refer to the 'How to update plugins' section in the API documentation.

Changes for third-party App developers

To maintain app's compatibility with Trados Studio 2022 SR1 following the way language metadata is handled, make sure to:

  • update the RequiredProduct details within the pluginpackage.manifest.xml file to mirror the latest software version.
  • check that any code referencing the Sdl.Core.Globalization.Language now references Sdl.Core.Globalization.Async instead.
  • consider the shift to using the custom language registry provided by Trados Studio rather than Microsoft's registry.