From 20fdb35751910616d55924a6ccdb5d81232227a1 Mon Sep 17 00:00:00 2001 From: Emanuel Albu Date: Tue, 17 Feb 2026 12:02:39 +0100 Subject: [PATCH 1/5] Add "How to update plugins in Trados Studio" page --- ...pdate_plugins_to_trados_studio_2024_sr1.md | 257 ------------------ ...o_update_plugins_to_trados_studio_2026.md} | 84 ++++-- articles/toc.yml | 6 +- 3 files changed, 67 insertions(+), 280 deletions(-) delete mode 100644 articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2024_sr1.md rename articles/hints_tips/Update_Plugins/{how_to_update_plugins_to_trados_studio_2024.md => how_to_update_plugins_to_trados_studio_2026.md} (58%) diff --git a/articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2024_sr1.md b/articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2024_sr1.md deleted file mode 100644 index eb18dc91f..000000000 --- a/articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2024_sr1.md +++ /dev/null @@ -1,257 +0,0 @@ -# How to update plugins to Trados Studio 2024 SR1 - -The following are a list of changes and known issues to consider when updating your plugin to be compatible with Trados Studio 2024 SR1. - -## Update Plugin Framework Packages -Ensure you are using the latest plugin framework NuGet packages: -- **Sdl.Core.PluginFramework:** v2.1.0 -- **Sdl.Core.PluginFramework.Build:** v18.0.1 - -**How to update:** -- In Solution Explorer, right-click **References > Manage NuGet Packages.** -- Set http://nuget.org as your package source. -- Search, select, and install/update the above packages. -- Accept license agreements to complete installation. - - -## Update Plugin Manifest - -Review and update the manifest (`pluginpackage.manifest.xml`) at the project root as in the following example: -```xml - - - My plugin name - 1.1.0.0 - My plugin description - Trados AppStore Team - - -``` -Ensure **RequiredProduct** reflects `minversion="18.1"` and `maxversion="18.1.9"`. - - -## Project References & Deployment Path -Update references and deployment settings in your .csproj: - -### [Production](#tab/standard) - -**References**: Set Trados Studio assemblies to use the Studio 18 path: -~~~xml - - $(MSBuildProgramFiles32)\Trados\Trados Studio\Studio18\Sdl.Desktop.IntegrationApi.Extensions.dll - -~~~ - -**Deployment Path:** -~~~xml -$(AppData)\Trados\Trados Studio\18\Plugins -~~~ - -### [BETA](#tab/beta) - -**References**: Set Trados Studio assemblies to use the Studio 18 Beta path: -~~~xml - - $(MSBuildProgramFiles32)\Trados\Trados Studio\Studio18Beta\Sdl.Desktop.IntegrationApi.Extensions.dll - -~~~ - -**Deployment Path:** -~~~xml -$(AppData)\Trados\Trados Studio\18Beta\Plugins -~~~ - ---- - -> [!NOTE] -> -> To update settings directly in the project file from Visual Studio -> * Right-click on the project node in the **Solution Explorer** and select **Unload Project**. -> * Then, right-click on the project and choose **Edit** -> -> Once you have applied your changes in the project file, then reload project -> * In the **Solution Explorer**, select the projects you want to load (press **Ctrl** while clicking to select more than one project) -> * Then right-click on the project and choose **Reload Project**. - -
- -## Known Issues & Dependency Updates -### Dependency Version Changes -Standalone integrations may require binding redirects. Example for `App.config`: -```xml - - - -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - -``` -
- -## Breaking API Changes - -### Assembly Version Change Requires Recompilation -With Trados Studio 2024 SR1, all core Trados assemblies have had their **assembly version increased to 18.1.x.x** (reflecting the semantic versioning minor update). **This assembly version bump introduces a breaking change:** Any plugin or standalone tool that references Trados assemblies must be recompiled against the new release, even if no other code changes are required. Referencing outdated assemblies is not supported and will likely result in runtime failures due to version mismatches. -
- -### Multiterm API Changes -**Migrate from `Sdl.Multiterm.TMO.Interop.dll` to `TerminologyProviderManager`** - -As part of the separation of MultiTerm from Trados Studio, the legacy assembly `Sdl.Multiterm.TMO.Interop.dll` **has been removed from the Trados Studio installation folder as of SR1**. Any integration or plugin referencing TMO interop must be updated: **the endorsed approach for terminology-related integrations moving forward is the `TerminologyProviderManager` singleton.** - -**How to migrate:** Use `Sdl.Terminology.TerminologyProvider.Core.TerminologyProviderManager.Instance` to access and initialize terminology providers. - -**Sample code:** -```csharp -using Sdl.Terminology.TerminologyProvider.Core; - -// Example URI for your termbase -string termbaseUriString = "file:///C:/Termbases/MyTermbase.sdltb"; -Uri termbaseUri = new Uri(termbaseUriString); - -// Get the terminology provider singleton instance -var terminologyProvider = TerminologyProviderManager.Instance.GetTerminologyProvider(termbaseUri); - -// Ensure the provider is initialized before searching -if (!terminologyProvider.IsInitialized) -{ - try - { - terminologyProvider.Initialize(); - } - catch (Exception ex) - { - // Handle initialization errors appropriately (log or surface meaningful error) - throw new InvalidOperationException("Failed to initialize terminology provider.", ex); - } -} - -// Set up search parameters -var sourceLanguage = new CultureInfo("en-US"); -var targetLanguage = new CultureInfo("it-IT"); -string segmentText = "Insert your source segment text here"; -int maxResultsCount = 10; -bool targetRequired = true; - -// Perform a fuzzy terminology search -var searchResults = terminologyProvider.Search( - segmentText, - sourceLanguage, - targetLanguage, - maxResultsCount, - SearchMode.Fuzzy, - targetRequired -); - -// Process or display results as needed... -``` -**Note:** Replace any references to `Sdl.Multiterm.TMO.Interop.dll` with the modern `TerminologyProviderManager` API. This ensures compatibility with Trados Studio 2024 SR1 and future releases, and aligns with Trados ongoing architectural updates. - -
- -## Credential Management Best Practices - -When building plugins or integrating third-party terminology and translation providers with Trados Studio, you should always manage credentials independently in your own codebase, especially when working with non-Trados services. - -**Key Points:** -- Built-in credential storage in Trados Studio is only required when you need to access native Trados resources (e.g., file-based translation memories, Language Cloud). -- For all other scenarios, including any third-party or custom service integration, you should implement your own secure mechanism for storing and retrieving credentials. -- Managing credentials independently enhances security and gives you greater flexibility and control. - -**Best Practice:** -Always use your own secure credential management system, unless your integration specifically requires direct access to Trados resources. - ---- - -### Example: Managing Credentials Securely -Below is an example showing how you can implement credential management using Windows Credential Manager. This strategy may be adapted to use other secure stores as required by your environment or policies. - -**Credential Store Interface:** -```csharp -public interface ICredentialStore -{ - void SaveCredential(string key, string username, string password); - (string Username, string Password)? GetCredential(string key); - void RemoveCredential(string key); -} -``` - -**Sample Windows Credential Manager Implementation** -*Install the [CredentialManagement](https://www.nuget.org/packages/CredentialManagement/) NuGet package for this sample:* - -```csharp -using CredentialManagement; - -public class WindowsCredentialStore : ICredentialStore -{ - public void SaveCredential(string key, string username, string password) - { - var cred = new Credential - { - Target = key, - Username = username, - Password = password, - PersistanceType = PersistanceType.LocalComputer - }; - cred.Save(); - } - - public (string Username, string Password)? GetCredential(string key) - { - var cred = new Credential { Target = key }; - if (cred.Load()) - { - return (cred.Username, cred.Password); - } - return null; - } - - public void RemoveCredential(string key) - { - var cred = new Credential { Target = key }; - cred.Delete(); - } -} -``` - -**How to Use in Your Integration** -```csharp -// Example usage -var credentialStore = new WindowsCredentialStore(); -var credentials = credentialStore.GetCredential("your-provider-key"); -if (credentials.HasValue) { - var username = credentials.Value.Username; - var password = credentials.Value.Password; - // Use credentials securely... -} else { - // Handle missing credentials scenario -} -``` -**Note:** Using your own credential store ensures future compatibility, enhances security, and keeps your integration flexible as Trados Studio and its APIs evolve. - diff --git a/articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2024.md b/articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2026.md similarity index 58% rename from articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2024.md rename to articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2026.md index 5b2e48506..02e25c2af 100644 --- a/articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2024.md +++ b/articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2026.md @@ -1,6 +1,23 @@ -# How to update plugins to Trados Studio 2024 +# How to update plugins in Trados Studio -The following are a list of changes and known issues to consider when updating your plugin to be compatible with Trados Studio 2024. +The following are a list of changes and known issues to consider when updating your plugin to be compatible with Trados Studio 2026. + +## Transition to 64-Bit (x64) +Studio Quantum is released as a 64-bit (x64) version. As a result, plug-ins must also be rebuilt and updated to target x64 in order to remain compatible. + +The following element must be added in a global property group of the .csproj file to target x64: + + +```xml + + ... + x64 + ... + +``` +> [!NOTE] +> +> If the project is not SDK-style, x64 must be set for all relevant configurations (e.g., Debug and Release), otherwise some builds may still compile for a different platform. ## Plugin Framework The latest version of the plugin framework packages should be installed. You can add/update the plugin framework nuget packages in your project via the package manager user interface or console. @@ -21,8 +38,8 @@ The manifest file **pluginpackage.manifest.xml** is located at the root of your ### RequiredProduct -- Min version should be set to: 18.0. -- Max version should be set to 18.9. It is recommended to also set this value, as it will provide the AppStore with sufficient information in correctly identifying plugins that are compatible with the version of Trados Studio that is launched. +- Min version should be set to: 19.0. +- Max version should be set to 19.9. It is recommended to also set this value, as it will provide the AppStore with sufficient information in correctly identifying plugins that are compatible with the version of Trados Studio that is launched. - Name should be set to: *TradosStudio* Example @@ -33,41 +50,41 @@ Example 1.1.0.0 My plugin description Trados AppStore Team - + ``` ## Project References & Deployment Path -The references in the project file (.csproj) should be mapped to the new installation path for Trados Studio 2024. Make reference to the following examples for both the production and beta releases. +The references in the project file (.csproj) should be mapped to the new installation path for Trados Studio 2026. Make reference to the following examples for both the production and beta releases. ### [Production](#tab/standard) -Installation path: *$(MSBuildProgramFiles32)\Trados\Trados Studio\Studio18*: +Installation path: *$(ProgramFiles)\Trados\Trados Studio\Studio19*: ~~~xml - $(MSBuildProgramFiles32)\Trados\Trados Studio\Studio18\Sdl.Desktop.IntegrationApi.Extensions.dll + $(ProgramFiles)\Trados\Trados Studio\Studio19\Sdl.Desktop.IntegrationApi.Extensions.dll ~~~
-Plugin deployment path: *$(AppData)\Trados\Trados Studio\18\Plugins*: +Plugin deployment path: *$(AppData)\Trados\Trados Studio\19\Plugins*: ~~~xml -$(AppData)\Trados\Trados Studio\18\Plugins +$(AppData)\Trados\Trados Studio\19\Plugins ~~~ ### [BETA](#tab/beta) -Installation path: *$(MSBuildProgramFiles32)\Trados\Trados Studio\Studio18Beta*: +Installation path: *$(ProgramFiles)\Trados\Trados Studio\Studio19Beta*: ~~~xml - $(MSBuildProgramFiles32)\Trados\Trados Studio\Studio18Beta\Sdl.Desktop.IntegrationApi.Extensions.dll + $(ProgramFiles)\Trados\Trados Studio\Studio19Beta\Sdl.Desktop.IntegrationApi.Extensions.dll ~~~
-Plugin deployment path: *$(AppData)\Trados\Trados Studio\18Beta\Plugins*: +Plugin deployment path: *$(AppData)\Trados\Trados Studio\19Beta\Plugins*: ~~~xml -$(AppData)\Trados\Trados Studio\18Beta\Plugins +$(AppData)\Trados\Trados Studio\19Beta\Plugins ~~~ --- @@ -81,15 +98,44 @@ Plugin deployment path: *$(AppData)\Trados\Trados Studio\18Beta\Plugins*: > Once you have applied your changes in the project file, then reload project > * In the **Solution Explorer**, select the projects you want to load (press **Ctrl** while clicking to select more than one project) > * Then right-click on the project and choose **Reload Project**. - -
-
+> +> If the project is SDK-style, then unloading/reloading is unnecessary. ## Known Issues The following are a list of known issues and solutions that you might encounter depending on your settings and configuration: +### Breaking API Changes +`ITerminologyProviderCredentialStore` was removed (together with method parameters of this type). + +`TerminologyProviderManager.DefaultTerminologyCredentialStore` was removed. + +`public TerminologyProviderType Type` property removed from `ITerminologyProvider` + +#### Assembly Version Change Requires Recompilation +With Trados Studio 2026, all core Trados assemblies have had their assembly version increased to 19.x.x.x (reflecting the semantic versioning minor update). This assembly version bump introduces a breaking change: Any plugin or standalone tool that references Trados assemblies must be recompiled against the new release, even if no other code changes are required. Referencing outdated assemblies is not supported and will likely result in runtime failures due to version mismatches. + +#### Working with BCMs +The BCM-related classes have been moved from Sdl.LanguagePlatform.TranslationMemoryApito TradosStudio.BcmLite: +```xml + + C:\Program Files\Trados\Trados Studio\Studio19\TradosStudio.BcmLite.dll + +``` +And some classes were renamed: + +`LiteDocument` to `Document` + +`LiteFragment` to `DocumentFragment` + +The `LiteBcmVisitor` abstract class now includes two more methods: + +```cs +public abstract void VisitFeedbackContainer(FeedbackContainer feedbackContainer); +public abstract void VisitStructure(StructureTag structureTag); +``` + ### Trados.Community.Toolkit (formally SDL.Community.Toolkit) -A new version of the Trados Community Toolkit, version 5.0.1, has been released to support the latest version of Trados Studio 2024. This includes the following assemblies: +A new version of the Trados Community Toolkit, version 6.0.2, has been released to support the latest version of Trados Studio 2026. This includes the following assemblies: - [Trados.Community.Toolkit.Core](https://www.nuget.org/packages/Trados.Community.Toolkit.Core) - [Trados.Community.Toolkit.LanguagePlatform](https://www.nuget.org/packages/Trados.Community.Toolkit.LanguagePlatform) @@ -98,7 +144,7 @@ A new version of the Trados Community Toolkit, version 5.0.1, has been released - [Trados.Community.Toolkit.ProjectAutomation](https://www.nuget.org/packages/Trados.Community.Toolkit.ProjectAutomation) ### Dependency version changes -There is a list of known dependency version changes that may influence your integration with the latest Trados Studio 2024 APIs; this is typically seen from standalone applications that are running outside of the Trados Studio context. To resolve these references, include the following binding redirects in the configuration file of the project. +There is a list of known dependency version changes that may influence your integration with the latest Trados Studio 2026 APIs; this is typically seen from standalone applications that are running outside of the Trados Studio context. To resolve these references, include the following binding redirects in the configuration file of the project. ``` xml diff --git a/articles/toc.yml b/articles/toc.yml index 4187b5c81..3d355102b 100644 --- a/articles/toc.yml +++ b/articles/toc.yml @@ -24,10 +24,8 @@ href: hints_tips/Better_Studio_interactivity/SR2ApiArticle.md - name: Studio Look & Feel in your 3rd party plugin href: hints_tips/Studio_Styles/StudioStyles.md - - name: How to update plugins to Trados Studio 2024 - href: hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2024.md - - name: How to update plugins to Trados Studio 2024 SR1 - href: hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2024_sr1.md + - name: How to update plugins to Trados Studio 2026 + href: hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2026.md - name: How to implement the Studio Useful Tips service href: hints_tips/UsefulTips/UsefulTipsApiArticle.md - name: How to implement an AI Companion From bd087e33a2062980f43b62cd5b3f503c71d5863c Mon Sep 17 00:00:00 2001 From: Emanuel Albu Date: Tue, 17 Feb 2026 13:12:09 +0100 Subject: [PATCH 2/5] ... --- ...to_update_plugins_to_trados_studio_2026.md | 172 ++++++++++++------ 1 file changed, 113 insertions(+), 59 deletions(-) diff --git a/articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2026.md b/articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2026.md index 02e25c2af..21b510e27 100644 --- a/articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2026.md +++ b/articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2026.md @@ -1,6 +1,6 @@ # How to update plugins in Trados Studio -The following are a list of changes and known issues to consider when updating your plugin to be compatible with Trados Studio 2026. +The following are a list of changes and known issues to consider when updating your plugin to be compatible with Trados Studio - 2026 Release. ## Transition to 64-Bit (x64) Studio Quantum is released as a 64-bit (x64) version. As a result, plug-ins must also be rebuilt and updated to target x64 in order to remain compatible. @@ -19,70 +19,59 @@ The following element must be added in a global property group of the .csproj fi > > If the project is not SDK-style, x64 must be set for all relevant configurations (e.g., Debug and Release), otherwise some builds may still compile for a different platform. -## Plugin Framework -The latest version of the plugin framework packages should be installed. You can add/update the plugin framework nuget packages in your project via the package manager user interface or console. -### Package Manager UI -* In **Solution Explorer**, right-click **References** and choose **Manage NuGet Packages**. -* Select nuget.org as the **Package source**. -* Search for `Sdl.Core.PluginFramework` from the **Browse** tab. -* Select the package from the list and click **Install** or **Update**. - * `Sdl.Core.PluginFramework`, version _2.1.0_ - * `Sdl.Core.PluginFramework.Build`, version _18.0.1_ -* Accept any license prompts to finnish the installation. +## Update Plugin Framework Packages +Ensure you are using the latest plugin framework NuGet packages: +- **Sdl.Core.PluginFramework:** v2.1.0 +- **Sdl.Core.PluginFramework.Build:** v18.0.1 -
+**How to update:** +- In Solution Explorer, right-click **References > Manage NuGet Packages.** +- Set http://nuget.org as your package source. +- Search, select, and install/update the above packages. +- Accept license agreements to complete installation. -## Plugin Manifest +## Update Plugin Manifest -The manifest file **pluginpackage.manifest.xml** is located at the root of your project solution. The values of the **RequiredProduct** should be updated to align with the latest release. - -### RequiredProduct - -- Min version should be set to: 19.0. -- Max version should be set to 19.9. It is recommended to also set this value, as it will provide the AppStore with sufficient information in correctly identifying plugins that are compatible with the version of Trados Studio that is launched. -- Name should be set to: *TradosStudio* - -Example +Review and update the manifest (`pluginpackage.manifest.xml`) at the project root as in the following example: ```xml My plugin name - 1.1.0.0 + 1.0.0.0 My plugin description Trados AppStore Team ``` +Ensure **RequiredProduct** reflects `minversion="19.0"` and `maxversion="19.9"`. ## Project References & Deployment Path -The references in the project file (.csproj) should be mapped to the new installation path for Trados Studio 2026. Make reference to the following examples for both the production and beta releases. +Update references and deployment settings in your .csproj: ### [Production](#tab/standard) -Installation path: *$(ProgramFiles)\Trados\Trados Studio\Studio19*: +**References**: Set Trados Studio assemblies to use the Studio 19 path: ~~~xml $(ProgramFiles)\Trados\Trados Studio\Studio19\Sdl.Desktop.IntegrationApi.Extensions.dll ~~~ -
-Plugin deployment path: *$(AppData)\Trados\Trados Studio\19\Plugins*: +**Deployment Path:** ~~~xml $(AppData)\Trados\Trados Studio\19\Plugins ~~~ ### [BETA](#tab/beta) -Installation path: *$(ProgramFiles)\Trados\Trados Studio\Studio19Beta*: +**References**: Set Trados Studio assemblies to use the Studio 19 Beta path: ~~~xml $(ProgramFiles)\Trados\Trados Studio\Studio19Beta\Sdl.Desktop.IntegrationApi.Extensions.dll ~~~ -
-Plugin deployment path: *$(AppData)\Trados\Trados Studio\19Beta\Plugins*: +**Deployment Path:** ~~~xml $(AppData)\Trados\Trados Studio\19Beta\Plugins ~~~ @@ -101,19 +90,50 @@ Plugin deployment path: *$(AppData)\Trados\Trados Studio\19Beta\Plugins*: > > If the project is SDK-style, then unloading/reloading is unnecessary. -## Known Issues +## Known Issues & Dependency Updates The following are a list of known issues and solutions that you might encounter depending on your settings and configuration: - +### Dependency version changes +Standalone integrations may require binding redirects. Example for `App.config`: +```xml + + + +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` ### Breaking API Changes `ITerminologyProviderCredentialStore` was removed (together with method parameters of this type). `TerminologyProviderManager.DefaultTerminologyCredentialStore` was removed. `public TerminologyProviderType Type` property removed from `ITerminologyProvider` - -#### Assembly Version Change Requires Recompilation -With Trados Studio 2026, all core Trados assemblies have had their assembly version increased to 19.x.x.x (reflecting the semantic versioning minor update). This assembly version bump introduces a breaking change: Any plugin or standalone tool that references Trados assemblies must be recompiled against the new release, even if no other code changes are required. Referencing outdated assemblies is not supported and will likely result in runtime failures due to version mismatches. - #### Working with BCMs The BCM-related classes have been moved from Sdl.LanguagePlatform.TranslationMemoryApito TradosStudio.BcmLite: ```xml @@ -134,8 +154,64 @@ public abstract void VisitFeedbackContainer(FeedbackContainer feedbackContainer) public abstract void VisitStructure(StructureTag structureTag); ``` +#### Assembly Version Change Requires Recompilation +With Trados Studio - 2026 Release, all core Trados assemblies have had their **assembly version increased to 19.x.x.x** (reflecting the semantic versioning minor update). **This assembly version bump introduces a breaking change:** Any plugin or standalone tool that references Trados assemblies must be recompiled against the new release, even if no other code changes are required. Referencing outdated assemblies is not supported and will likely result in runtime failures due to version mismatches. +### Multiterm API Changes +**Migrate from `Sdl.Multiterm.TMO.Interop.dll` to `TerminologyProviderManager`** + +As part of the separation of MultiTerm from Trados Studio, the legacy assembly `Sdl.Multiterm.TMO.Interop.dll` **has been removed from the Trados Studio installation folder as of SR1**. Any integration or plugin referencing TMO interop must be updated: **the endorsed approach for terminology-related integrations moving forward is the `TerminologyProviderManager` singleton.** + +**How to migrate:** Use `Sdl.Terminology.TerminologyProvider.Core.TerminologyProviderManager.Instance` to access and initialize terminology providers. + +**Sample code:** +```csharp +using Sdl.Terminology.TerminologyProvider.Core; + +// Example URI for your termbase +string termbaseUriString = "file:///C:/Termbases/MyTermbase.sdltb"; +Uri termbaseUri = new Uri(termbaseUriString); + +// Get the terminology provider singleton instance +var terminologyProvider = TerminologyProviderManager.Instance.GetTerminologyProvider(termbaseUri); + +// Ensure the provider is initialized before searching +if (!terminologyProvider.IsInitialized) +{ + try + { + terminologyProvider.Initialize(); + } + catch (Exception ex) + { + // Handle initialization errors appropriately (log or surface meaningful error) + throw new InvalidOperationException("Failed to initialize terminology provider.", ex); + } +} + +// Set up search parameters +var sourceLanguage = new CultureInfo("en-US"); +var targetLanguage = new CultureInfo("it-IT"); +string segmentText = "Insert your source segment text here"; +int maxResultsCount = 10; +bool targetRequired = true; + +// Perform a fuzzy terminology search +var searchResults = terminologyProvider.Search( + segmentText, + sourceLanguage, + targetLanguage, + maxResultsCount, + SearchMode.Fuzzy, + targetRequired +); + +// Process or display results as needed... +``` +**Note:** Replace any references to `Sdl.Multiterm.TMO.Interop.dll` with the modern `TerminologyProviderManager` API. This ensures compatibility with Trados Studio - 2026 Release and future releases, and aligns with Trados ongoing architectural updates. + + ### Trados.Community.Toolkit (formally SDL.Community.Toolkit) -A new version of the Trados Community Toolkit, version 6.0.2, has been released to support the latest version of Trados Studio 2026. This includes the following assemblies: +A new version of the Trados Community Toolkit, version 6.0.2, has been released to support the latest version of Trados Studio - 2026 Release. This includes the following assemblies: - [Trados.Community.Toolkit.Core](https://www.nuget.org/packages/Trados.Community.Toolkit.Core) - [Trados.Community.Toolkit.LanguagePlatform](https://www.nuget.org/packages/Trados.Community.Toolkit.LanguagePlatform) @@ -143,25 +219,3 @@ A new version of the Trados Community Toolkit, version 6.0.2, has been released - [Trados.Community.Toolkit.FileType](https://www.nuget.org/packages/Trados.Community.Toolkit.FileType) - [Trados.Community.Toolkit.ProjectAutomation](https://www.nuget.org/packages/Trados.Community.Toolkit.ProjectAutomation) -### Dependency version changes -There is a list of known dependency version changes that may influence your integration with the latest Trados Studio 2026 APIs; this is typically seen from standalone applications that are running outside of the Trados Studio context. To resolve these references, include the following binding redirects in the configuration file of the project. - -``` xml - - - - - - - - - - - - - - - - - -``` From f4c897a4cc9d72707c7c55d54e83b393d98692c6 Mon Sep 17 00:00:00 2001 From: Emanuel Albu Date: Wed, 18 Feb 2026 13:22:53 +0100 Subject: [PATCH 3/5] Update MultiTerm API Changes --- .../how_to_update_plugins_to_trados_studio_2026.md | 14 +++++++++++--- 1 file changed, 11 insertions(+), 3 deletions(-) diff --git a/articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2026.md b/articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2026.md index 21b510e27..7ec00b88f 100644 --- a/articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2026.md +++ b/articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2026.md @@ -168,7 +168,7 @@ As part of the separation of MultiTerm from Trados Studio, the legacy assembly ` using Sdl.Terminology.TerminologyProvider.Core; // Example URI for your termbase -string termbaseUriString = "file:///C:/Termbases/MyTermbase.sdltb"; +string termbaseUriString = "ttb.file:///C:/Termbases/MyTermbase.ttb"; Uri termbaseUri = new Uri(termbaseUriString); // Get the terminology provider singleton instance @@ -189,8 +189,16 @@ if (!terminologyProvider.IsInitialized) } // Set up search parameters -var sourceLanguage = new CultureInfo("en-US"); -var targetLanguage = new CultureInfo("it-IT"); +var sourceLanguage = new DefinitionLanguage +{ + Locale = "EN", + Name = "English" +}; +var targetLanguage = new DefinitionLanguage +{ + Locale = "DE", + Name = "German" +}; string segmentText = "Insert your source segment text here"; int maxResultsCount = 10; bool targetRequired = true; From 8b3b721e405892e0e716b319dc4315471f9a7bde Mon Sep 17 00:00:00 2001 From: Emanuel Albu Date: Wed, 18 Feb 2026 13:37:29 +0100 Subject: [PATCH 4/5] ... --- .../how_to_update_plugins_to_trados_studio_2026.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2026.md b/articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2026.md index 7ec00b88f..c714f2935 100644 --- a/articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2026.md +++ b/articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2026.md @@ -138,7 +138,7 @@ Standalone integrations may require binding redirects. Example for `App.config`: The BCM-related classes have been moved from Sdl.LanguagePlatform.TranslationMemoryApito TradosStudio.BcmLite: ```xml - C:\Program Files\Trados\Trados Studio\Studio19\TradosStudio.BcmLite.dll + $(ProgramFiles)\Trados\Trados Studio\Studio19\TradosStudio.BcmLite.dll ``` And some classes were renamed: From 2b2513a8b8c7ed7f157ddd9c8be3084784ab1e18 Mon Sep 17 00:00:00 2001 From: Emanuel Albu Date: Wed, 18 Feb 2026 14:00:49 +0100 Subject: [PATCH 5/5] ... --- .../how_to_update_plugins_to_trados_studio_2026.md | 2 +- articles/toc.yml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2026.md b/articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2026.md index c714f2935..7c924e4b0 100644 --- a/articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2026.md +++ b/articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2026.md @@ -1,4 +1,4 @@ -# How to update plugins in Trados Studio +# How to update plugins to Trados Studio - 2026 Release The following are a list of changes and known issues to consider when updating your plugin to be compatible with Trados Studio - 2026 Release. diff --git a/articles/toc.yml b/articles/toc.yml index 3d355102b..54efe8bd1 100644 --- a/articles/toc.yml +++ b/articles/toc.yml @@ -24,7 +24,7 @@ href: hints_tips/Better_Studio_interactivity/SR2ApiArticle.md - name: Studio Look & Feel in your 3rd party plugin href: hints_tips/Studio_Styles/StudioStyles.md - - name: How to update plugins to Trados Studio 2026 + - name: How to update plugins to Trados Studio - 2026 Release href: hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2026.md - name: How to implement the Studio Useful Tips service href: hints_tips/UsefulTips/UsefulTipsApiArticle.md