From a8b1819ce0d2f2e28d5e632e8fccffdaa3bec826 Mon Sep 17 00:00:00 2001
From: "github-actions[bot]" <github-actions[bot]@users.noreply.sdl.com>
Date: Thu, 19 Feb 2026 15:09:06 +0000
Subject: [PATCH] Update generated documentation

---
 README.html                                   |  12 +-
 .../setting_up_the_visual_studio_project.html |   4 +-
 apiconcepts/core/overview.html                |   2 +-
 .../core/the_plugin_manifest_generator.html   |   2 +-
 .../build_the_file_type_plug_in.html          |   8 +-
 .../create_a_new_bil_project.html             |   2 +-
 .../create_a_new_native_project.html          |   2 +-
 ...ng_a_new_assembly_for_the_settings_ui.html |   2 +-
 .../creating_a_new_bil_project.html           |   2 +-
 .../creating_a_new_project.html               |   2 +-
 ..._a_trados_studio_commandLineProcessor.html |   2 +-
 .../setting_up_the_visual_studio_project.html |   2 +-
 .../integration/studio_automation.html        |   4 +-
 .../user_interface_integration.html           |   4 +-
 .../about_project_files.html                  |   2 +-
 .../required_references_and_namespaces.html   |   2 +-
 .../setting_the_project_information.html      |   4 +-
 .../setting_up_the_visual_studio_project.html |   2 +-
 apiconcepts/releasenotes/overview.html        |   4 +-
 .../releasenotes/tradosstudio2022.html        |   8 +-
 .../releasenotes/tradosstudio2022sr1.html     |  10 +-
 .../releasenotes/tradosstudio2022sr2.html     |   8 +-
 .../releasenotes/tradosstudio2024.html        |   6 +-
 .../releasenotes/tradosstudio2024sr1.html     |   6 +-
 .../settingup_the_visual_studio_project.html  |   4 +-
 .../building_the_plugin.html                  |   4 +-
 .../verification/create_a_new_project.html    |   2 +-
 .../gettingstarted/building_a_plugin.html     |   4 +-
 .../gettingstarted/community_plugins.html     |   2 +-
 .../gettingstarted/plugin_deployment.html     |   4 +-
 .../setting_up_a_developer_machine.html       |  18 +-
 ..._update_plugins_to_trados_studio_2024.html | 243 ------------------
 ...update_plugins_to_trados_studio_2026.html} | 161 +++++-------
 articles/toc.html                             |   5 +-
 articles/toc.json                             |   2 +-
 index.html                                    |  15 +-
 index.json                                    |  15 +-
 manifest.json                                 |  14 +-
 38 files changed, 155 insertions(+), 440 deletions(-)
 delete mode 100644 articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2024.html
 rename articles/hints_tips/Update_Plugins/{how_to_update_plugins_to_trados_studio_2024_sr1.html => how_to_update_plugins_to_trados_studio_2026.html} (70%)

diff --git a/README.html b/README.html
index 805ca407b..cad38f619 100644
--- a/README.html
+++ b/README.html
@@ -122,13 +122,13 @@ <h3 id="getting-started-with-your-contribution">Getting started with your contri
 </li>
 <li><p>Our documentation automatically fills in the product name and other details so you don't have to make the changes manually if we decide to update the product name. Use the '<a href="var:VariableName">var:VariableName</a>' construct to tell our documentation engine to fill in the info for you. Here are the constructs available at this point:</p>
 <pre><code>Trados Studio - The product name, for example Trados Studio
-Trados Studio 2024 SR1 - The official product release name including the edition, for example 'Trados Studio 2021'
-Studio18 - the official product version, for example Studio16
-18 - the official product version number, such as 16
+Trados Studio 2026 Release - The official product release name including the edition, for example 'Trados Studio 2021'
+Studio19 - the official product version, for example Studio16
+19 - the official product version number, such as 16
 Microsoft Visual Studio 2022 - the most recent development compatible Microsoft Visual Studio edition
-%AppData%\Trados\Trados Studio\18\Plugins\Packages\ - the location where plugins are deployed, for example '%AppData%\Roaming\SDL\SDL Trados Studio\16\Plugins\Packages\'
-%AppData%\Trados\Trados Studio\18\Plugins\Unpacked\ - the location where plugins are unpacked, for example '%AppData%\Roaming\SDL\SDL Trados Studio\16\Plugins\Unpacked\'
-C:\Program Files (x86)\Trados\Trados Studio\Studio18 - the current installation folder of our product, for example 'C:\Program Files\SDL\SDL Trados Studio\Studio16\'
+%AppData%\Trados\Trados Studio\19\Plugins\Packages\ - the location where plugins are deployed, for example '%AppData%\Roaming\SDL\SDL Trados Studio\16\Plugins\Packages\'
+%AppData%\Trados\Trados Studio\19\Plugins\Unpacked\ - the location where plugins are unpacked, for example '%AppData%\Roaming\SDL\SDL Trados Studio\16\Plugins\Unpacked\'
+C:\Program Files (x86)\Trados\Trados Studio\Studio19 - the current installation folder of our product, for example 'C:\Program Files\SDL\SDL Trados Studio\Studio16\'
 </code></pre>
 </li>
 </ul>
diff --git a/apiconcepts/batchtasks/setting_up_the_visual_studio_project.html b/apiconcepts/batchtasks/setting_up_the_visual_studio_project.html
index b96904839..c9d022d0c 100644
--- a/apiconcepts/batchtasks/setting_up_the_visual_studio_project.html
+++ b/apiconcepts/batchtasks/setting_up_the_visual_studio_project.html
@@ -129,9 +129,9 @@ <h5>Note</h5>
 </code></pre></section>
 </div>
 <h2 id="the-plug-in-build-folder">The Plug-in Build Folder</h2>
-<p>Make sure that you sign your assembly. Then build the assembly. The project is automatically configured to build the plug-in file into the folder: <em> %AppData%\Trados\Trados Studio\18\Plugins\Packages\ </em>. After you have built the plug-in, you should find the file <em>Custom Batch Task1.sdlplugin</em>. Now start Trados Studio. Because the plug-in is not yet officially signed by RWS, you will see the following message after you start the application:
+<p>Make sure that you sign your assembly. Then build the assembly. The project is automatically configured to build the plug-in file into the folder: <em> %AppData%\Trados\Trados Studio\19\Plugins\Packages\ </em>. After you have built the plug-in, you should find the file <em>Custom Batch Task1.sdlplugin</em>. Now start Trados Studio. Because the plug-in is not yet officially signed by RWS, you will see the following message after you start the application:
 <img style="display:block; " src="images/Plugin_NotSigned.jpg">
-For the moment, ignore this message. Click <strong>Yes</strong> to make sure that Trados Studio extracts the plug-in file. Once Studio is started, you should find the sub-folder <em>Custom Batch Task1</em> under <em> %AppData%\Trados\Trados Studio\18\Plugins\Unpacked\ </em>. This sub-folder contains the unpacked plug-in assemblies.</p>
+For the moment, ignore this message. Click <strong>Yes</strong> to make sure that Trados Studio extracts the plug-in file. Once Studio is started, you should find the sub-folder <em>Custom Batch Task1</em> under <em> %AppData%\Trados\Trados Studio\19\Plugins\Unpacked\ </em>. This sub-folder contains the unpacked plug-in assemblies.</p>
 <p>In the batch tasks list of Trados Studio, you will see the name of your newly compiled plug-in:
 <img style="display:block; " src="images/SampleTaskName.jpg"></p>
 <p>When you select your sample batch task you will see the following window with the plug-in description:
diff --git a/apiconcepts/core/overview.html b/apiconcepts/core/overview.html
index 56978d716..fd1ff65b5 100644
--- a/apiconcepts/core/overview.html
+++ b/apiconcepts/core/overview.html
@@ -84,7 +84,7 @@ <h1 id="plug-in-framework-overview">Plug-in Framework Overview</h1>
 
 <p>This help system describes the Plug-in Framework. This framework offers plug-in functionality to applications and components. Application developers can define extension points and dynamically load any plug-ins providing extensions targeting these extension points using the plug-in framework.</p>
 <h2 id="version">Version</h2>
-<p>The version of the Plug-in Framework documented here is the one that was released with Trados Studio 2024 SR1.</p>
+<p>The version of the Plug-in Framework documented here is the one that was released with Trados Studio 2026 Release.</p>
 <h2 id="main-concepts-and-definitions">Main Concepts and Definitions</h2>
 <p>This section introduces a number of concepts and definitions that are central to the plug-in framework.</p>
 <ul>
diff --git a/apiconcepts/core/the_plugin_manifest_generator.html b/apiconcepts/core/the_plugin_manifest_generator.html
index 217eaf9f8..2d1e1b4c6 100644
--- a/apiconcepts/core/the_plugin_manifest_generator.html
+++ b/apiconcepts/core/the_plugin_manifest_generator.html
@@ -109,7 +109,7 @@ <h2 id="plug-in-manifest-generator">Plug-in Manifest Generator</h2>
 <p>When creating a plug-in project using the project template from the SDK, the project file will contain the following pieces of custom content:</p>
 <ul>
 <li><code>CreatePluginPackage</code> - if set to true will generate the <code>*.sdlplugin</code></li>
-<li><code>PluginDeploymentPath</code> - path to the root folder where the <code>Packages</code> and <code>Unpacked</code> folders are present, default path is set to <em>%AppData%\Trados\Trados Studio\18\Plugins\Packages\</em></li>
+<li><code>PluginDeploymentPath</code> - path to the root folder where the <code>Packages</code> and <code>Unpacked</code> folders are present, default path is set to <em>%AppData%\Trados\Trados Studio\19\Plugins\Packages\</em></li>
 </ul>
 
 </article>
diff --git a/apiconcepts/filetypesupport/build_the_file_type_plug_in.html b/apiconcepts/filetypesupport/build_the_file_type_plug_in.html
index cfb9bb490..6b390cab2 100644
--- a/apiconcepts/filetypesupport/build_the_file_type_plug_in.html
+++ b/apiconcepts/filetypesupport/build_the_file_type_plug_in.html
@@ -94,11 +94,11 @@ <h2 id="the-plug-in-package-path">The Plug-in Package Path</h2>
 <p>In order for Trados Studio to pick up the plug-in package and to extract it, the following folders need to be available on your hard drive:</p>
 <p><strong>For Windows 10\ Windows 7\ Windows 8</strong>:</p>
 <ul>
-<li>%AppData%\Trados\Trados Studio\18\Plugins\Packages\ *</li>
+<li>%AppData%\Trados\Trados Studio\19\Plugins\Packages\ *</li>
 </ul>
 <p>and</p>
 <ul>
-<li>%AppData%\Trados\Trados Studio\18\Plugins\Unpacked\ *</li>
+<li>%AppData%\Trados\Trados Studio\19\Plugins\Unpacked\ *</li>
 </ul>
 <p>Make sure that you place the *<em>.sdlplugin</em> file into the sub-folder Packages and launch Trados Studio. During startup of Trados Studio the content of the package will be automatically extracted to the Unpacked sub-folder, as illustrated below:</p>
 <p>The above folder does not have to be the build output path, but it is convenient to build the project in this folder, as this will also create the *<em>.sdlplugin</em> file where it needs to be. After creating the plug-in based on the (empty) template, you could already build the project. However, it will, of course, not offer any functionality.</p>
@@ -145,10 +145,10 @@ <h2 id="build-and-debug-suggestions">Build and Debug Suggestions</h2>
 <p>Here are a couple of simple suggestions to help buld and debug your plug-in.</p>
 <ul>
 <li>Change your solution and project so that it runs Trados Studio by default.</li>
-<li>Change your project so that it the output is directed to the Trados Studio plug-in package directory - this will automatically deploy your plug-in. In Windows 7, the -in package directory is stored in %AppData%\Trados\Trados Studio\18\Plugins\Packages\.</li>
+<li>Change your project so that it the output is directed to the Trados Studio plug-in package directory - this will automatically deploy your plug-in. In Windows 7, the -in package directory is stored in %AppData%\Trados\Trados Studio\19\Plugins\Packages\.</li>
 <li>Change your project so that it deletes the previous unpacked version of your plug-in - this will ensure that Studio uses the latest version of your plug-in. This can be done using a post-build event.</li>
 </ul>
-<pre><code class="lang-txt">rmdir /S /Q &quot;%AppData%\Trados\Trados Studio\18\Plugins\Unpacked\ \Sdl.Sdk.FileTypeSupport.Samples.Bil&quot;
+<pre><code class="lang-txt">rmdir /S /Q &quot;%AppData%\Trados\Trados Studio\19\Plugins\Unpacked\ \Sdl.Sdk.FileTypeSupport.Samples.Bil&quot;
 </code></pre>
 <h2 id="see-also">See Also</h2>
 <p><a href="creating_a_new_project.html">Creating a New Project</a></p>
diff --git a/apiconcepts/filetypesupport/create_a_new_bil_project.html b/apiconcepts/filetypesupport/create_a_new_bil_project.html
index 6a50ab300..0c767d1f0 100644
--- a/apiconcepts/filetypesupport/create_a_new_bil_project.html
+++ b/apiconcepts/filetypesupport/create_a_new_bil_project.html
@@ -96,7 +96,7 @@ <h2 id="add-the-required-references">Add the Required References</h2>
 <ul>
 <li><strong>Sdl.Core.Settings.dll</strong></li>
 <li><strong>Sdl.Core.PluginFramework.dll</strong>
-By default you will find these files in the Trados Studio installation folder, e.g. <em>C:\Program Files (x86)\Trados\Trados Studio\Studio18</em>. The <strong>Copy Local</strong> property for these references should be set to True.</li>
+By default you will find these files in the Trados Studio installation folder, e.g. <em>C:\Program Files (x86)\Trados\Trados Studio\Studio19</em>. The <strong>Copy Local</strong> property for these references should be set to True.</li>
 </ul>
 <p><img src="images/BilingualVerifierReferences.jpg" alt="BilingualVerifierReferences"></p>
 <div class="NOTE">
diff --git a/apiconcepts/filetypesupport/create_a_new_native_project.html b/apiconcepts/filetypesupport/create_a_new_native_project.html
index c6c8d8014..e5abb1496 100644
--- a/apiconcepts/filetypesupport/create_a_new_native_project.html
+++ b/apiconcepts/filetypesupport/create_a_new_native_project.html
@@ -97,7 +97,7 @@ <h2 id="add-the-required-references">Add the Required References</h2>
 <li><strong>Sdl.Core.Settings.dll</strong></li>
 <li><strong>Sdl.Core.PluginFramework.dll</strong></li>
 </ul>
-<p>By default you find these files in the Trados Studio installation folder, usually <em>C:\Program Files (x86)\Trados\Trados Studio\Studio18</em>. The <strong>Copy Local</strong> property for these references should be set to True.</p>
+<p>By default you find these files in the Trados Studio installation folder, usually <em>C:\Program Files (x86)\Trados\Trados Studio\Studio19</em>. The <strong>Copy Local</strong> property for these references should be set to True.</p>
 <p><img src="images/NativeVerifierReferences.jpg" alt="NativeVerifierReferences"></p>
 <div class="NOTE">
 <h5>Note</h5>
diff --git a/apiconcepts/filetypesupport/creating_a_new_assembly_for_the_settings_ui.html b/apiconcepts/filetypesupport/creating_a_new_assembly_for_the_settings_ui.html
index 363dd08ac..2ec7b953a 100644
--- a/apiconcepts/filetypesupport/creating_a_new_assembly_for_the_settings_ui.html
+++ b/apiconcepts/filetypesupport/creating_a_new_assembly_for_the_settings_ui.html
@@ -97,7 +97,7 @@ <h2 id="add-the-required-references">Add the Required References</h2>
 <li><strong>Sdl.Core.Settings.dll</strong></li>
 <li><strong>Sdl.FileTypeSupport.Framework.Core.Settings.dll</strong></li>
 </ul>
-<p>Set the output path for building your project to the installation folder of Trados Studio, e.g. <em>C:\Program Files (x86)\Trados\Trados Studio\Studio18</em>.</p>
+<p>Set the output path for building your project to the installation folder of Trados Studio, e.g. <em>C:\Program Files (x86)\Trados\Trados Studio\Studio19</em>.</p>
 <h2 id="see-also">See Also</h2>
 <p><a href="implementing_the_settings_ui.html">Implementing the Settings UI</a></p>
 <p><a href="implementing_the_ui_controller_class.html">Implementing the UI Controller Class</a></p>
diff --git a/apiconcepts/filetypesupport/creating_a_new_bil_project.html b/apiconcepts/filetypesupport/creating_a_new_bil_project.html
index 46b0e3f11..c1daaf796 100644
--- a/apiconcepts/filetypesupport/creating_a_new_bil_project.html
+++ b/apiconcepts/filetypesupport/creating_a_new_bil_project.html
@@ -98,7 +98,7 @@ <h2 id="add-the-required-references">Add the Required References</h2>
 <li><strong>Sdl.Core.PluginFramework.dll</strong></li>
 <li><strong>Sdl.Core.Settings.dll</strong></li>
 </ul>
-<p>By default you find these files in the Trados Studio installation folder, usually <em>C:\Program Files (x86)\Trados\Trados Studio\Studio18</em>. The <strong>Copy Local</strong> property for these references should be set to True.</p>
+<p>By default you find these files in the Trados Studio installation folder, usually <em>C:\Program Files (x86)\Trados\Trados Studio\Studio19</em>. The <strong>Copy Local</strong> property for these references should be set to True.</p>
 <p>Remember to generate a key to sign the assembly. It is also recommended that you set <strong>SDLTradosStudio.exe</strong> as the external application for debugging purposes.</p>
 <h2 id="add-the-required-resources">Add the Required Resources</h2>
 <p>Add a resources file (<em>Resources.resx</em>) to the project's properties. We will use this resources file later for storing information text on the file type plug-in that will be exposed in the user interface of Trados Studio.</p>
diff --git a/apiconcepts/filetypesupport/creating_a_new_project.html b/apiconcepts/filetypesupport/creating_a_new_project.html
index 33500455f..ab736ca18 100644
--- a/apiconcepts/filetypesupport/creating_a_new_project.html
+++ b/apiconcepts/filetypesupport/creating_a_new_project.html
@@ -95,7 +95,7 @@ <h2 id="add-the-required-references">Add the Required References</h2>
 <li><strong>Sdl.Core.Globalization.dll</strong></li>
 <li><strong>Sdl.FileTypeSupport.Framework.Core.Utilities</strong></li>
 </ul>
-<p>By default these files can be found in the installation folder of Trados Studio, i.e. <em>C:\Program Files (x86)\Trados\Trados Studio\Studio18</em>. The 'Copy Local' property for these references should be set to True.</p>
+<p>By default these files can be found in the installation folder of Trados Studio, i.e. <em>C:\Program Files (x86)\Trados\Trados Studio\Studio19</em>. The 'Copy Local' property for these references should be set to True.</p>
 <p><img src="images/NativeFilterRef.jpg" alt="NativeFilterRef"></p>
 <div class="NOTE">
 <h5>Note</h5>
diff --git a/apiconcepts/integration/create_a_trados_studio_commandLineProcessor.html b/apiconcepts/integration/create_a_trados_studio_commandLineProcessor.html
index 166ef2c2d..c25aee589 100644
--- a/apiconcepts/integration/create_a_trados_studio_commandLineProcessor.html
+++ b/apiconcepts/integration/create_a_trados_studio_commandLineProcessor.html
@@ -92,7 +92,7 @@ <h2 id="creating-a-varproductname-command-line-argument-processor">Creating a Tr
 </li>
 </ul>
 <p>If you don't implement <a href="../../api/integration/Sdl.Desktop.IntegrationApi.Extensions.CommandLine.IExternalCommandLineProcessor.html">IExternalCommandLineProcessor</a> or <a href="../../api/integration/Sdl.Desktop.IntegrationApi.Extensions.CommandLine.IExternalWindowAwareCommandLineProcessor.html">IExternalWindowAwareCommandLineProcessor</a>,  an exception will be thrown, but if you omit the <a href="../../api/integration/Sdl.Desktop.IntegrationApi.Extensions.CommandLine.ExternalCommandLineProcessorAttribute.html">ExternalCommandLineProcessorAttribute</a>, your plugin will simply be ignored when Trados Studio starts.</p>
-<p>After successfully creating your command line processor you can check the Help generated for it by and running the following command in cmd.exe : C:\Program Files (x86)\Trados\Trados Studio\Studio18\SdlTradosStudio.exe ? . Your command will appear, among other commands available, in the following screen :
+<p>After successfully creating your command line processor you can check the Help generated for it by and running the following command in cmd.exe : C:\Program Files (x86)\Trados\Trados Studio\Studio19\SdlTradosStudio.exe ? . Your command will appear, among other commands available, in the following screen :
 <img style="display:block; " src="images/cmdHelpWindow.jpg"></p>
 <p>[Creating a Trados Studio Command line processor Sample]
 (trados_studio_command_processor.md)</p>
diff --git a/apiconcepts/integration/setting_up_the_visual_studio_project.html b/apiconcepts/integration/setting_up_the_visual_studio_project.html
index 3fd5049ee..48d68ebee 100644
--- a/apiconcepts/integration/setting_up_the_visual_studio_project.html
+++ b/apiconcepts/integration/setting_up_the_visual_studio_project.html
@@ -93,7 +93,7 @@ <h2 id="how-to-create-the-visual-studio-project">How to create the Visual Studio
 <div class="IMPORTANT">
 <h5>Important</h5>
 <p>The <em>The Sdl.Core.Globalization</em> assembly is not automatically added to the project with the Trados Studio (2021) template. This assembly will be required for this project, as we will be making reference to some of the <a href="../../api/filetypesupport/Sdl.FileTypeSupport.Framework.BilingualApi.ISegmentPair.html">ISegmentPair</a> enumerators.</p>
-<p>To add this assembly, from the Solution Explorer, right-click on the <strong>References</strong> node and click <strong>Add Reference</strong> from the context menu. Then, navigate to the <strong>C:\Program Files (x86)\Trados\Trados Studio\Studio18</strong> and select the <strong>Sdl.Core.Globalization.dll file</strong>.</p>
+<p>To add this assembly, from the Solution Explorer, right-click on the <strong>References</strong> node and click <strong>Add Reference</strong> from the context menu. Then, navigate to the <strong>C:\Program Files (x86)\Trados\Trados Studio\Studio19</strong> and select the <strong>Sdl.Core.Globalization.dll file</strong>.</p>
 </div>
 <h2 id="how-to-sign-the-solution">How to sign the solution</h2>
 <p>To sign your development solution from the project properties area.</p>
diff --git a/apiconcepts/integration/studio_automation.html b/apiconcepts/integration/studio_automation.html
index 51e48bd2d..3565c6dd3 100644
--- a/apiconcepts/integration/studio_automation.html
+++ b/apiconcepts/integration/studio_automation.html
@@ -98,8 +98,8 @@ <h1 id="introduction">Introduction</h1>
 </ul>
 <div class="NOTE">
 <h5>Note</h5>
-<p>As build output path for your implementations please choose the <em>%AppData%\Trados\Trados Studio\18\Plugins\Packages\</em>.</p>
-<p>Also check that your library references are pointing to the Trados Studio folder. e.g. <em>C:\Program Files (x86)\Trados\Trados Studio\Studio18</em>.</p>
+<p>As build output path for your implementations please choose the <em>%AppData%\Trados\Trados Studio\19\Plugins\Packages\</em>.</p>
+<p>Also check that your library references are pointing to the Trados Studio folder. e.g. <em>C:\Program Files (x86)\Trados\Trados Studio\Studio19</em>.</p>
 <p>For more information on how to build and deploy a Studio plug-in, see (Building a plug-in and Plug-in deployment)</p>
 <p>Sign and use Strong-Named Assemblies to enable the loading of your plug-ins inside the Trados Studio.</p>
 <p><a href="https://docs.microsoft.com/en-us/dotnet/standard/assembly/sign-strong-name?redirectedfrom=MSDN">How to: Sign an Assembly with a Strong Name</a></p>
diff --git a/apiconcepts/integration/user_interface_integration.html b/apiconcepts/integration/user_interface_integration.html
index 23b1d1b9e..88a70c344 100644
--- a/apiconcepts/integration/user_interface_integration.html
+++ b/apiconcepts/integration/user_interface_integration.html
@@ -93,8 +93,8 @@ <h1 id="introduction">Introduction</h1>
 </ul>
 <div class="NOTE">
 <h5>Note</h5>
-<p>As build output path for your implementations please choose the <em>%AppData%\Trados\Trados Studio\18\Plugins\Packages\</em>.</p>
-<p>Also check that your library references are pointing to the Trados Studio folder. e.g. <em>C:\Program Files (x86)\Trados\Trados Studio\Studio18</em>.</p>
+<p>As build output path for your implementations please choose the <em>%AppData%\Trados\Trados Studio\19\Plugins\Packages\</em>.</p>
+<p>Also check that your library references are pointing to the Trados Studio folder. e.g. <em>C:\Program Files (x86)\Trados\Trados Studio\Studio19</em>.</p>
 <p>For more information on building an deploying a Trados Studio plug-in, see (Building a plug-in and Plug-in deployment).</p>
 <p>Sign and use Strong-Named Assemblies to enable the loading of your plug-ins inside the Trados Studio.</p>
 </div>
diff --git a/apiconcepts/projectautomation/about_project_files.html b/apiconcepts/projectautomation/about_project_files.html
index 2fd84ec34..d9b8c6dcb 100644
--- a/apiconcepts/projectautomation/about_project_files.html
+++ b/apiconcepts/projectautomation/about_project_files.html
@@ -112,7 +112,7 @@ <h2 id="reference-files">Reference Files</h2>
 <p>Reference files are files that need to be part of the project, for instance for preview reasons, but that can be changed as part of the project. Reference files are language files, which means they are associated with a particular project language.</p>
 <p>Reference files are represented by the <code>IReferenceFile</code> interface in the object model.</p>
 <img style="display:block; " src="images/NewProject03.jpg">
-<p>The screenshot above illustrates how project files are selected in Trados Studio 2024 SR1.</p>
+<p>The screenshot above illustrates how project files are selected in Trados Studio 2026 Release.</p>
 <h2 id="see-also">See also</h2>
 <p><a href="adding_files_and_folders.html">Adding Files and Folders</a></p>
 <p><a href="creating_a_merged_file.html">Creating a Merged File</a></p>
diff --git a/apiconcepts/projectautomation/required_references_and_namespaces.html b/apiconcepts/projectautomation/required_references_and_namespaces.html
index 694c76686..bd420fa09 100644
--- a/apiconcepts/projectautomation/required_references_and_namespaces.html
+++ b/apiconcepts/projectautomation/required_references_and_namespaces.html
@@ -109,7 +109,7 @@ <h2 id="namespaces-to-use">Namespaces to Use</h2>
 <h2 id="further-requirements">Further Requirements</h2>
 <p>In addition to the above, you should observer the following:</p>
 <ul>
-<li>As build output location choose the installation folder of Trados Studio , e.g. <em>C:\Program Files (x86)\Trados\Trados Studio\Studio18</em></li>
+<li>As build output location choose the installation folder of Trados Studio , e.g. <em>C:\Program Files (x86)\Trados\Trados Studio\Studio19</em></li>
 <li>Configure your projects as x84 applications, as otherwise they will not work when running on 64 bit platforms. Therefore, set the platform target of your projects to x84.</li>
 </ul>
 <h2 id="references-from-the-translation-memory-api">References from the Translation Memory API</h2>
diff --git a/apiconcepts/projectautomation/setting_the_project_information.html b/apiconcepts/projectautomation/setting_the_project_information.html
index 727440a51..7f020b4db 100644
--- a/apiconcepts/projectautomation/setting_the_project_information.html
+++ b/apiconcepts/projectautomation/setting_the_project_information.html
@@ -137,7 +137,7 @@ <h2 id="set-the-project-information">Set the Project Information</h2>
 <p>The screenshot below illustrates how this information is entered in the <strong>New Project</strong> wizard of Trados Studio.
 <img src="images/NewProject01.jpg" alt="NewProject01"></p>
 <h2 id="set-the-local-project-folder">Set the Local Project Folder</h2>
-<p>All project files, i.e. translatable and localizable documents, reference files, project TMs, etc. are stored in a specific folder. By default, the main folder used for storing projects is: C:\Users\UserName\Documents\Studio 2024\Projects. Below this main folder Trados Studio creates sub-folders that carry the name of the respective project. However, you could just as well pick any other folder name, as long as the specified folder is empty so as to avoid collisions with existing files. In the example below we follow the default folder rule of Trados Studio by selecting the Studio 2024\Projects\ folder below Documents, and by appending the project name sub-folder. We then set the <a href="../../api/projectautomation/Sdl.ProjectAutomation.Core.ProjectInfo.html#Sdl_ProjectAutomation_Core_ProjectInfo_LocalProjectFolder">LocalProjectFolder</a> property accordingly as shown in the example below:</p>
+<p>All project files, i.e. translatable and localizable documents, reference files, project TMs, etc. are stored in a specific folder. By default, the main folder used for storing projects is: C:\Users\UserName\Documents\Studio 2026 Release\Projects. Below this main folder Trados Studio creates sub-folders that carry the name of the respective project. However, you could just as well pick any other folder name, as long as the specified folder is empty so as to avoid collisions with existing files. In the example below we follow the default folder rule of Trados Studio by selecting the Studio 2026 Release\Projects\ folder below Documents, and by appending the project name sub-folder. We then set the <a href="../../api/projectautomation/Sdl.ProjectAutomation.Core.ProjectInfo.html#Sdl_ProjectAutomation_Core_ProjectInfo_LocalProjectFolder">LocalProjectFolder</a> property accordingly as shown in the example below:</p>
 <div class="tabGroup" id="tabgroup_4">
 <ul role="tablist">
 <li role="presentation">
@@ -218,7 +218,7 @@ <h2 id="select-the-project-languages">Select the Project Languages</h2>
 After running the above code you should already see a result in the projects folder as illustrated in the screenshot below:
 <img src="images/FoldersAfterProjectInfo.jpg" alt="FoldersAfterProjectInfo"></p>
 <p>Even if you have not added any translatable files yet, you will end up generating the project sub-folder (i.e. Projects\My first project), which contains the *.sdlproj file. In the following chapters you will learn how to add documents, TMs, termbases, etc. to turn your sample into a meaningful project. Note that if you run your sample application again while the My first project is still there, an error will be thrown, as the folder is not empty. It is recommended that when you re-run your sample application for testing purposes that you delete the project sub-folder, so that you have a fresh start (see also <a href="deleting_projects.html">Deleting Projects</a>).</p>
-<p>Also note that the C:\Users\UserName\Documents\Studio 2024\Projects folder contains a file called projects.xml. This is a meta file that contains references to all the projects that have been created in Trados Studio. The projects that you create programmatically will not be referenced in this file, and thus not be listed in Trados Studio, which is by design. However, you can, of course, open the programmatically created *.sdlproj file in Trados Studio.</p>
+<p>Also note that the C:\Users\UserName\Documents\Studio 2026 Release\Projects folder contains a file called projects.xml. This is a meta file that contains references to all the projects that have been created in Trados Studio. The projects that you create programmatically will not be referenced in this file, and thus not be listed in Trados Studio, which is by design. However, you can, of course, open the programmatically created *.sdlproj file in Trados Studio.</p>
 <h2 id="putting-it-all-together">Putting it All Together</h2>
 <p>The complete function for setting the project properties should look as shown below:</p>
 <div class="tabGroup" id="tabgroup_9">
diff --git a/apiconcepts/projectautomation/setting_up_the_visual_studio_project.html b/apiconcepts/projectautomation/setting_up_the_visual_studio_project.html
index cefa7fa72..595dd540a 100644
--- a/apiconcepts/projectautomation/setting_up_the_visual_studio_project.html
+++ b/apiconcepts/projectautomation/setting_up_the_visual_studio_project.html
@@ -101,7 +101,7 @@ <h1 id="setting-up-the-visual-studio-project">Setting up the Visual Studio Proje
 <li>Sdl.LanguagePlatform.TranslationMemoryApi.dll</li>
 </ul>
 <p>Note that we require the functionality of the Translation Memory API to access information on the selected TM, i.e. the source / target language combination. Note that this is a case in point of how the Project Automation API and the Translation Memory API are sometimes required to be leveraged both to implement the functionality of your applications.</p>
-<p>Make sure to set the project build output location to the Trados Studio installation folder, e.g. <em>C:\Program Files (x86)\Trados\Trados Studio\Studio18</em>. <strong>Important note</strong>: Set the platform target of your projects to x86.</p>
+<p>Make sure to set the project build output location to the Trados Studio installation folder, e.g. <em>C:\Program Files (x86)\Trados\Trados Studio\Studio19</em>. <strong>Important note</strong>: Set the platform target of your projects to x86.</p>
 <h2 id="see-also">See Also</h2>
 <p><a href="required_references_and_namespaces.html">Required References and Namespaces</a></p>
 
diff --git a/apiconcepts/releasenotes/overview.html b/apiconcepts/releasenotes/overview.html
index 65b25924f..a2658c492 100644
--- a/apiconcepts/releasenotes/overview.html
+++ b/apiconcepts/releasenotes/overview.html
@@ -82,8 +82,8 @@
             <article class="content wrap" id="_content" data-uid="">
 <h1 id="varproductname-api-release-notes">Trados Studio API Release Notes</h1>
 
-<p>A list of API changes released together with Trados Studio 2024 SR1.
-<a href="tradosstudio2024.html">API Changes for Trados Studio 2024 SR1</a></p>
+<p>A list of API changes released together with Trados Studio 2026 Release.
+<a href="tradosstudio2024.html">API Changes for Trados Studio 2026 Release</a></p>
 
 </article>
           </div>
diff --git a/apiconcepts/releasenotes/tradosstudio2022.html b/apiconcepts/releasenotes/tradosstudio2022.html
index 7b95c349a..81134b395 100644
--- a/apiconcepts/releasenotes/tradosstudio2022.html
+++ b/apiconcepts/releasenotes/tradosstudio2022.html
@@ -5,9 +5,9 @@
   <head>
     <meta charset="utf-8">
       <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
-      <title>Release Notes for Trados Studio 2024 SR1 </title>
+      <title>Release Notes for Trados Studio 2026 Release </title>
       <meta name="viewport" content="width=device-width">
-      <meta name="title" content="Release Notes for Trados Studio 2024 SR1 ">
+      <meta name="title" content="Release Notes for Trados Studio 2026 Release ">
     
     
       <link rel="shortcut icon" href="../../favicon.ico">
@@ -80,10 +80,10 @@
         <div class="article row grid-right">
           <div class="col-md-10">
             <article class="content wrap" id="_content" data-uid="">
-<h1 id="release-notes-for-varproductnamewithedition">Release Notes for Trados Studio 2024 SR1</h1>
+<h1 id="release-notes-for-varproductnamewithedition">Release Notes for Trados Studio 2026 Release</h1>
 
 <h1 id="groupshare-2015-integration">Groupshare 2015 Integration</h1>
-<p>As of Trados Studio 2024 SR1 the integration with Groupshare 2015 is EOL. Therefore the our public APIs no longer offer the support and any code references have been removed.</p>
+<p>As of Trados Studio 2026 Release the integration with Groupshare 2015 is EOL. Therefore the our public APIs no longer offer the support and any code references have been removed.</p>
 <h1 id="project-automation-api">Project Automation API</h1>
 <h3 id="new-properties-on-projectinfo">New properties on <a href="../../api/projectautomation/Sdl.ProjectAutomation.Core.ProjectInfo.html">ProjectInfo</a></h3>
 <p>We expanded the <a href="../../api/projectautomation/Sdl.ProjectAutomation.Core.ProjectInfo.html">ProjectInfo</a> class to include information regarding the current user associated to the project.
diff --git a/apiconcepts/releasenotes/tradosstudio2022sr1.html b/apiconcepts/releasenotes/tradosstudio2022sr1.html
index 27b6e0adc..f7c90dc60 100644
--- a/apiconcepts/releasenotes/tradosstudio2022sr1.html
+++ b/apiconcepts/releasenotes/tradosstudio2022sr1.html
@@ -5,9 +5,9 @@
   <head>
     <meta charset="utf-8">
       <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
-      <title>Release Notes for Trados Studio 2024 SR1 SR1 </title>
+      <title>Release Notes for Trados Studio 2026 Release SR1 </title>
       <meta name="viewport" content="width=device-width">
-      <meta name="title" content="Release Notes for Trados Studio 2024 SR1 SR1 ">
+      <meta name="title" content="Release Notes for Trados Studio 2026 Release SR1 ">
     
     
       <link rel="shortcut icon" href="../../favicon.ico">
@@ -80,10 +80,10 @@
         <div class="article row grid-right">
           <div class="col-md-10">
             <article class="content wrap" id="_content" data-uid="">
-<h1 id="release-notes-for-varproductnamewithedition-sr1">Release Notes for Trados Studio 2024 SR1 SR1</h1>
+<h1 id="release-notes-for-varproductnamewithedition-sr1">Release Notes for Trados Studio 2026 Release SR1</h1>
 
 <h1 id="retargeted-assemblies">Retargeted assemblies</h1>
-<p>Some of the available APIs provided along with Trados Studio 2024 SR1 have been retargeted from .NET Framework 4.8 to .NET Standard for better compatibility options and richer overall support.</p>
+<p>Some of the available APIs provided along with Trados Studio 2026 Release have been retargeted from .NET Framework 4.8 to .NET Standard for better compatibility options and richer overall support.</p>
 <p>At the time of this release, the retargeted assemblies are as follows:
 | Parent API                           | Assembly                                             |
 |--------------------------------------|------------------------------------------------------|
@@ -261,7 +261,7 @@ <h1 id="general-api-changes">General API changes</h1>
 ```
 </code></pre>
 <h1 id="dependency-version-changes">Dependency version changes</h1>
-<p>The following is a list of known dependency version changes that may influence your integration with the latest Trados Studio 2024 SR1 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.</p>
+<p>The following is a list of known dependency version changes that may influence your integration with the latest Trados Studio 2026 Release 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.</p>
 <pre><code class="lang-xml">&lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot;?&gt;
 &lt;configuration&gt;
   &lt;startup useLegacyV2RuntimeActivationPolicy=&quot;true&quot;&gt;
diff --git a/apiconcepts/releasenotes/tradosstudio2022sr2.html b/apiconcepts/releasenotes/tradosstudio2022sr2.html
index 4425958f3..7a0bbc7d6 100644
--- a/apiconcepts/releasenotes/tradosstudio2022sr2.html
+++ b/apiconcepts/releasenotes/tradosstudio2022sr2.html
@@ -5,9 +5,9 @@
   <head>
     <meta charset="utf-8">
       <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
-      <title>Release Notes for Trados Studio 2024 SR1 SR2 </title>
+      <title>Release Notes for Trados Studio 2026 Release SR2 </title>
       <meta name="viewport" content="width=device-width">
-      <meta name="title" content="Release Notes for Trados Studio 2024 SR1 SR2 ">
+      <meta name="title" content="Release Notes for Trados Studio 2026 Release SR2 ">
     
     
       <link rel="shortcut icon" href="../../favicon.ico">
@@ -80,13 +80,13 @@
         <div class="article row grid-right">
           <div class="col-md-10">
             <article class="content wrap" id="_content" data-uid="">
-<h1 id="release-notes-for-varproductnamewithedition-sr2">Release Notes for Trados Studio 2024 SR1 SR2</h1>
+<h1 id="release-notes-for-varproductnamewithedition-sr2">Release Notes for Trados Studio 2026 Release SR2</h1>
 
 <h1 id="added-api-licensing-support-for-subscriptions">Added API licensing support for subscriptions</h1>
 <p>When creating standalone apps, you can now use Project automation API calls that need a license even if Trados Studio is licensed through a subscription. This expands the list of supported scenarios where Trados Studio is licensed through a perpetual license, or through a network server license.</p>
 <div class="NOTE">
 <h5>Note</h5>
-<p>Starting with Trados Studio 2024 SR1 SR2, when developing a standalone application using Project Automation APIs that require a license, make sure to call <code>LicenseManager.ReleaseLicense()</code> before the application exits. See <a href="../projectautomation/overview.html">Project Automation Overview</a> for more details.</p>
+<p>Starting with Trados Studio 2026 Release SR2, when developing a standalone application using Project Automation APIs that require a license, make sure to call <code>LicenseManager.ReleaseLicense()</code> before the application exits. See <a href="../projectautomation/overview.html">Project Automation Overview</a> for more details.</p>
 </div>
 <h1 id="terminology-provider">Terminology Provider</h1>
 <p>The changes are included in <code>Sdl.Terminology.TerminologyProvider.Core</code>.</p>
diff --git a/apiconcepts/releasenotes/tradosstudio2024.html b/apiconcepts/releasenotes/tradosstudio2024.html
index e915cda16..ef5f329ed 100644
--- a/apiconcepts/releasenotes/tradosstudio2024.html
+++ b/apiconcepts/releasenotes/tradosstudio2024.html
@@ -5,9 +5,9 @@
   <head>
     <meta charset="utf-8">
       <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
-      <title>Release Notes for Trados Studio 2024 SR1 </title>
+      <title>Release Notes for Trados Studio 2026 Release </title>
       <meta name="viewport" content="width=device-width">
-      <meta name="title" content="Release Notes for Trados Studio 2024 SR1 ">
+      <meta name="title" content="Release Notes for Trados Studio 2026 Release ">
     
     
       <link rel="shortcut icon" href="../../favicon.ico">
@@ -80,7 +80,7 @@
         <div class="article row grid-right">
           <div class="col-md-10">
             <article class="content wrap" id="_content" data-uid="">
-<h1 id="release-notes-for-varproductnamewithedition">Release Notes for Trados Studio 2024 SR1</h1>
+<h1 id="release-notes-for-varproductnamewithedition">Release Notes for Trados Studio 2026 Release</h1>
 
 <h1 id="trados-studio-automation">Trados Studio Automation</h1>
 <p>The changes are included in <code>Sdl.TranslationStudioAutomation.IntegrationApi</code>.</p>
diff --git a/apiconcepts/releasenotes/tradosstudio2024sr1.html b/apiconcepts/releasenotes/tradosstudio2024sr1.html
index ded182b87..7e9ed7699 100644
--- a/apiconcepts/releasenotes/tradosstudio2024sr1.html
+++ b/apiconcepts/releasenotes/tradosstudio2024sr1.html
@@ -5,9 +5,9 @@
   <head>
     <meta charset="utf-8">
       <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
-      <title>Release Notes for Trados Studio 2024 SR1 SR1 </title>
+      <title>Release Notes for Trados Studio 2026 Release SR1 </title>
       <meta name="viewport" content="width=device-width">
-      <meta name="title" content="Release Notes for Trados Studio 2024 SR1 SR1 ">
+      <meta name="title" content="Release Notes for Trados Studio 2026 Release SR1 ">
     
     
       <link rel="shortcut icon" href="../../favicon.ico">
@@ -80,7 +80,7 @@
         <div class="article row grid-right">
           <div class="col-md-10">
             <article class="content wrap" id="_content" data-uid="">
-<h1 id="release-notes-for-varproductnamewithedition-sr1">Release Notes for Trados Studio 2024 SR1 SR1</h1>
+<h1 id="release-notes-for-varproductnamewithedition-sr1">Release Notes for Trados Studio 2026 Release SR1</h1>
 
 <h1 id="multiterm-tmo-interop">MultiTerm TMO Interop</h1>
 <p><code>Sdl.Multiterm.TMO.Interop.dll</code> is no longer present in the install folder after the separation from MultiTerm.</p>
diff --git a/apiconcepts/terminology/settingup_the_visual_studio_project.html b/apiconcepts/terminology/settingup_the_visual_studio_project.html
index 1fddb7d19..92dc66de6 100644
--- a/apiconcepts/terminology/settingup_the_visual_studio_project.html
+++ b/apiconcepts/terminology/settingup_the_visual_studio_project.html
@@ -115,9 +115,9 @@ <h2 id="the-plug-in-declaration-id-name-description">The Plug-in Declaration: ID
 <p>Make sure the resource file access modifier is set to <em>public</em> and that you treat it as an <em>embedded</em> resource.</p>
 <p>Open the <strong>MyTerminologyProviderWinFormsUI.cs</strong> class. This class controls how the plug-in manifests in the Trados Studio UI. Change the <strong>TypeName</strong> and <strong>TypeDescription</strong> members as shown below.</p>
 <h2 id="how-to-build-and-load-the-plugin-in-varproductname">How to build and load the plugin in Trados Studio</h2>
-<p>Build the assembly. The project is automatically configured to build the plug-in file into the <em>%AppData%\Trados\Trados Studio\18\Plugins\Packages\</em> folder. After you have built the plug-in, you should find the Terminology Provider1.sdlplugin file in the folder. Start Trados Studio. As the plug-in is not yet officially signed by RWS, you will see the following message when starting the application:
+<p>Build the assembly. The project is automatically configured to build the plug-in file into the <em>%AppData%\Trados\Trados Studio\19\Plugins\Packages\</em> folder. After you have built the plug-in, you should find the Terminology Provider1.sdlplugin file in the folder. Start Trados Studio. As the plug-in is not yet officially signed by RWS, you will see the following message when starting the application:
 <img style="display:block; " src="images/Plugin_NotSigned.jpg">
-For the moment, ignore this message and click <strong>Yes</strong> to make sure that Trados Studio extracts the plug-in file. Once Trados Studio is started, you should find the sub-folder <em>Terminology Provider1</em> under <em> %AppData%\Trados\Trados Studio\18\Plugins\Unpacked\ </em>. This sub-folder contains the unpacked plug-in assemblies.</p>
+For the moment, ignore this message and click <strong>Yes</strong> to make sure that Trados Studio extracts the plug-in file. Once Trados Studio is started, you should find the sub-folder <em>Terminology Provider1</em> under <em> %AppData%\Trados\Trados Studio\19\Plugins\Unpacked\ </em>. This sub-folder contains the unpacked plug-in assemblies.</p>
 <div class="NOTE">
 <h5>Note</h5>
 <p>To officially sign the plugin, send the sdlplugin file to app-signing@sdl.com.</p>
diff --git a/apiconcepts/translationmemory/building_the_plugin.html b/apiconcepts/translationmemory/building_the_plugin.html
index f0be3dae3..ccb1a35fb 100644
--- a/apiconcepts/translationmemory/building_the_plugin.html
+++ b/apiconcepts/translationmemory/building_the_plugin.html
@@ -91,9 +91,9 @@ <h1 id="building-the-plug-in">Building the Plug-in</h1>
 </ul>
 <p>In order for Trados Studio to pick up the plug-in package and to extract it, the following folders need to be available on your hard drive:</p>
 <p>**For Windows 10 / Windows 8.1 **:</p>
-<p>%AppData%\Trados\Trados Studio\18\Plugins\Packages\</p>
+<p>%AppData%\Trados\Trados Studio\19\Plugins\Packages\</p>
 <p>and</p>
-<p>%AppData%\Trados\Trados Studio\18\Plugins\Unpacked\</p>
+<p>%AppData%\Trados\Trados Studio\19\Plugins\Unpacked\</p>
 <p>Make sure that you place the *<em>.sdlplugin</em> file into the sub-folder Packages and launch Trados Studio. During startup of Trados Studio the content of the package will be automatically extracted to the <em>Unpacked</em> sub-folder, as illustrated below:</p>
 <img style="display:block; " src="images/PlugInUnpacked.jpg">
 <p>Upon start-up Trados Studio will load the unpacked plug-in and show the following message, which you can confirm with <strong>Yes</strong>, so that the plug-in gets loaded. This message appears when loading plug-ins that have not been certified by RWS, which could potentially be unsafe. The message can be avoided by submitting your plug-in to RWS for certification.</p>
diff --git a/apiconcepts/verification/create_a_new_project.html b/apiconcepts/verification/create_a_new_project.html
index 86fe4c64b..b6bb6c7d5 100644
--- a/apiconcepts/verification/create_a_new_project.html
+++ b/apiconcepts/verification/create_a_new_project.html
@@ -94,7 +94,7 @@ <h2 id="add-the-required-references">Add the Required References</h2>
 <li><strong>Sdl.FileTypeSupport.Framework.Core</strong></li>
 <li><strong>Sdl.Core.Settings.dll</strong></li>
 </ul>
-<p>By default, these files can be found in the installation folder of Trados Studio, i.e. <em>C:\Program Files (x86)\Trados\Trados Studio\Studio18</em>. The 'Copy Local' property for these references should be set to True.</p>
+<p>By default, these files can be found in the installation folder of Trados Studio, i.e. <em>C:\Program Files (x86)\Trados\Trados Studio\Studio19</em>. The 'Copy Local' property for these references should be set to True.</p>
 <img style="display:block; " src="images/GlobalVerifierRef.jpg">
 <div class="NOTE">
 <h5>Note</h5>
diff --git a/articles/gettingstarted/building_a_plugin.html b/articles/gettingstarted/building_a_plugin.html
index d2acd73e4..203035721 100644
--- a/articles/gettingstarted/building_a_plugin.html
+++ b/articles/gettingstarted/building_a_plugin.html
@@ -127,7 +127,7 @@ <h2 id="building-a-plug-in-1">Building a Plug-in</h2>
 <li><strong>Description</strong>: description of the plug-in package.</li>
 <li><strong>Author</strong>: the name of the plug-in author</li>
 <li><strong>RequiredProduct</strong>: this indicates which product this plug-in supports. This must include the minimum version and can optionally include a maximum version. <br>
-If the minimum version is set to <em>18.1</em> that means the plugin can be installed only in Trados Studio SR1 and above.</li>
+If the minimum version is set to <em>19.1</em> that means the plugin can be installed only in Trados Studio SR1 and above.</li>
 <li><strong>Include</strong>: a list of additional files to be included into the plugin package.</li>
 </ul>
 <p>Any plugin project need to have the following nuget packages refrenced :</p>
@@ -150,7 +150,7 @@ <h5>Note</h5>
 </li>
 <li>The plug-in package, <code>MyPlugin.sdlplugin</code> which contains all of the above, together with the plug-in package manifest. <br></li>
 </ul>
-<p>After all the relevant information was added, build the project. Plugin can be found at the following local path <em>%AppData%\Trados\Trados Studio\18\Plugins\Packages\</em> if the default path wasn't changed. <br></p>
+<p>After all the relevant information was added, build the project. Plugin can be found at the following local path <em>%AppData%\Trados\Trados Studio\19\Plugins\Packages\</em> if the default path wasn't changed. <br></p>
 <p>If in the console following error appears: <code>Error 1 Failed to locate ResGen.exe and unable to compile plug-in resource file...</code> please make sure you have installed <a href="https://dotnet.microsoft.com/en-us/download/dotnet-framework/net48">.Net Framework 4.8</a>.</p>
 <p>Now, we are ready to deploy the plug-in package in Trados Studio. See <a href="plugin_deployment.html">Plug-in deployment</a>.</p>
 
diff --git a/articles/gettingstarted/community_plugins.html b/articles/gettingstarted/community_plugins.html
index dfce7a174..31b5f9715 100644
--- a/articles/gettingstarted/community_plugins.html
+++ b/articles/gettingstarted/community_plugins.html
@@ -94,7 +94,7 @@ <h2 id="getting-started">Getting Started</h2>
 </li>
 <li><p>After the repository was cloned, navigate to the repository path you’ve specified when cloning the repository. Each plugin has a dedicated folder. All you need to do is to find the plugin you’re looking for, enter the folder and open the solution file using Microsoft Visual Studio.</p>
 </li>
-<li><p>Build the solution. After the build has succeeded, open Trados Studio 2024 SR1. Click “Yes” when the warning message appears. After Trados Studio loads, the built plugin will be available in Trados Studio.</p>
+<li><p>Build the solution. After the build has succeeded, open Trados Studio 2026 Release. Click “Yes” when the warning message appears. After Trados Studio loads, the built plugin will be available in Trados Studio.</p>
 </li>
 </ul>
 <img style="display:block; " src="images/UnsignedWarning.png">
diff --git a/articles/gettingstarted/plugin_deployment.html b/articles/gettingstarted/plugin_deployment.html
index 1dd295f60..bdf333d3f 100644
--- a/articles/gettingstarted/plugin_deployment.html
+++ b/articles/gettingstarted/plugin_deployment.html
@@ -87,14 +87,14 @@ <h2 id="installing-a-plug-in-package">Installing a Plug-in Package</h2>
 <p>Double click the plug-in package and follow the instructions.</p>
 <div class="NOTE">
 <h5>Note</h5>
-<p>During development, you can configure the output path of the project to point to <em>%AppData%\Trados\Trados Studio\18\Plugins\Packages\</em>. This is already configured if you created the project with one of the project templates available in the <strong>Trados Studio SDK</strong> here. For more information on this, see <a href="setting_up_a_developer_machine.html">Setting up a Developer Machine</a>.</p>
+<p>During development, you can configure the output path of the project to point to <em>%AppData%\Trados\Trados Studio\19\Plugins\Packages\</em>. This is already configured if you created the project with one of the project templates available in the <strong>Trados Studio SDK</strong> here. For more information on this, see <a href="setting_up_a_developer_machine.html">Setting up a Developer Machine</a>.</p>
 </div>
 <p>The following warning message will be shown while Trados Studio starts:
 <img style="display:block; " src="images/UnsignedWarning.png"></p>
 <p>To avoid this message from appearing, you need to submit your plug-in package to RWS for verification. Once verified, your plug-in package will be signed by RWS and the warning message will not appear anymore. To verify the plugin, send an email to <strong>app-signing@sdl.com</strong> with a link from where the plugin can be downloaded for verification. Once the verification is done, you will receive an answer email with a download link, where you will be able to obtain the signed version of the plugin.</p>
 <p>Once Trados Studio has started, go to the <strong>Tools &gt; Plug-ins</strong> dialog and notice that &quot;MyPlugin&quot; is now listed as a plug-in and is ready to be used.</p>
 <h2 id="updating-a-plug-in-package">Updating a Plug-in Package</h2>
-<p>Once deployed, you can update your plug-in package by increasing the version in the plug-in package manifest (see <a href="plugin_deployment.html">Plug-in deployment</a>). Double click the plug-in package and follow the instructions. Once the plug-in is deployed, start Trados Studio. The application will automatically detect the presence of the updated plug-in package, verify it, extract its contents into <em> %AppData%\Trados\Trados Studio\18\Plugins\Unpacked\ </em> and load it.</p>
+<p>Once deployed, you can update your plug-in package by increasing the version in the plug-in package manifest (see <a href="plugin_deployment.html">Plug-in deployment</a>). Double click the plug-in package and follow the instructions. Once the plug-in is deployed, start Trados Studio. The application will automatically detect the presence of the updated plug-in package, verify it, extract its contents into <em> %AppData%\Trados\Trados Studio\19\Plugins\Unpacked\ </em> and load it.</p>
 <p>It is essential that you increase the version of the plug-in package as listed in the plug-in manifest, or the update will not be applied.</p>
 <h2 id="uninstalling-a-plug-in-package">Uninstalling a Plug-in Package</h2>
 <p>To uninstall a plug-in, you have two options:</p>
diff --git a/articles/gettingstarted/setting_up_a_developer_machine.html b/articles/gettingstarted/setting_up_a_developer_machine.html
index 99e0acc7a..1e3490a76 100644
--- a/articles/gettingstarted/setting_up_a_developer_machine.html
+++ b/articles/gettingstarted/setting_up_a_developer_machine.html
@@ -86,7 +86,7 @@ <h1 id="setting-up-a-developer-machine">Setting up a Developer Machine</h1>
 <h2 id="prerequisites">Prerequisites</h2>
 <ul>
 <li>For the development environment, we recommend using Microsoft Visual Studio 2022.</li>
-<li>You need a licensed Trados Studio 2024 SR1 or later installed on your development machine</li>
+<li>You need a licensed Trados Studio 2026 Release or later installed on your development machine</li>
 <li>We also recommend installation of the <strong>Trados Studio SDK</strong> on your machine. Note that after the installation of <strong>Trados Studio SDK</strong>, the <strong>New Project</strong> dialog box from Microsoft Visual Studio 2022 will feature additional project templates specific to the Trados Studio application development.
 <ul>
 <li>You can get the latest version from the <a href="https://appstore.sdl.com/language/developers/sdk.html">developer hub</a>.</li>
@@ -95,25 +95,25 @@ <h2 id="prerequisites">Prerequisites</h2>
 </ul>
 </li>
 <li>If your implementations need to connect to a TM Server system, then make sure that the TM Server also runs the latest version.</li>
-<li>If you are developing against a version of API the which is distributed with one of SDL's publicly released applications (i.e. Trados Studio 2024 SR1), then all required assemblies and files should be available alongside the application. Make sure that you have the latest release of Trados Studio installed.</li>
+<li>If you are developing against a version of API the which is distributed with one of SDL's publicly released applications (i.e. Trados Studio 2026 Release), then all required assemblies and files should be available alongside the application. Make sure that you have the latest release of Trados Studio installed.</li>
 </ul>
 <div class="NOTE">
 <h5>Note</h5>
-<p>As build output path for your implementations please choose the %AppData%\Trados\Trados Studio\18\Plugins\Packages\</p>
-<p>Also check that your library references are pointing to the Trados Studio folder. e.g. C:\Program Files (x86)\Trados\Trados Studio\Studio18.</p>
+<p>As build output path for your implementations please choose the %AppData%\Trados\Trados Studio\19\Plugins\Packages\</p>
+<p>Also check that your library references are pointing to the Trados Studio folder. e.g. C:\Program Files (x86)\Trados\Trados Studio\Studio19.</p>
 <p>For more informations regarding how to build and deploy a Studio plug-in see <a href="building_a_plugin.html">Building a plug-in</a> and <a href="plugin_deployment.html">Plug-in deployment</a></p>
 <p>Sign and use Strong-Named Assemblies to enable the loading of your plug-ins inside Trados Studio. For more information see <a href="https://docs.microsoft.com/en-us/dotnet/standard/assembly/sign-strong-name?redirectedfrom=MSDN">How to: Sign an Assembly with a Strong Name</a> <br>
 If you don't have a key, you can download <a href="https://github.com/RWS/Sdl-Community">SdlCommunity.snk</a> key from public AppStore repository.</p>
 <p>Choosing a different build output path or not signing your assembly will prevent your plugin to be loaded.</p>
 </div>
-<h2 id="system-requirements-for-running-varproductnamewithedition">System requirements for running Trados Studio 2024 SR1:</h2>
+<h2 id="system-requirements-for-running-varproductnamewithedition">System requirements for running Trados Studio 2026 Release:</h2>
 <ul>
-<li>A Microsoft Windows-based PC or an Intel-based Apple Mac computer running Windows as an operating system. Trados Studio 2024 SR1 runs on the latest build of Windows 11 and the latest updated version of Windows 10.</li>
-<li>Up to 2.5 GB of available disk space to run the Trados Studio 2024 SR1 installer</li>
-<li>2 GB of available disk space to run Trados Studio 2024 SR1</li>
+<li>A Microsoft Windows-based PC or an Intel-based Apple Mac computer running Windows as an operating system. Trados Studio 2026 Release runs on the latest build of Windows 11 and the latest updated version of Windows 10.</li>
+<li>Up to 2.5 GB of available disk space to run the Trados Studio 2026 Release installer</li>
+<li>2 GB of available disk space to run Trados Studio 2026 Release</li>
 <li>A recent processor with dual or multi-core technology</li>
 <li>At least 8 GB RAM</li>
-<li>Trados Studio 2024 SR1 requires Microsoft .Net Framework 4.8.</li>
+<li>Trados Studio 2026 Release requires Microsoft .Net Framework 4.8.</li>
 <li>Additional details can be found on the <a href="https://docs.rws.com/binary/980998/802650/trados-studio-2022/trados-studio-release-notes">product release notes</a></li>
 </ul>
 <h2 id="system-requirements-for-running-sdl-groupshare--tm-server--multiterm--project-server">System requirements for running SDL GroupShare ( TM Server,  Multiterm,  Project Server):</h2>
diff --git a/articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2024.html b/articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2024.html
deleted file mode 100644
index 8fdbd3cf3..000000000
--- a/articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2024.html
+++ /dev/null
@@ -1,243 +0,0 @@
-<!DOCTYPE html>
-<!--[if IE]><![endif]-->
-<html>
-
-  <head>
-    <meta charset="utf-8">
-      <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
-      <title>How to update plugins to Trados Studio 2024 </title>
-      <meta name="viewport" content="width=device-width">
-      <meta name="title" content="How to update plugins to Trados Studio 2024 ">
-    
-    
-      <link rel="shortcut icon" href="../../../favicon.ico">
-      <link rel="stylesheet" href="../../../styles/docfx.vendor.min.css">
-      <link rel="stylesheet" href="../../../styles/docfx.css">
-      <link rel="stylesheet" href="../../../styles/main.css">
-      <meta property="docfx:navrel" content="../../../toc.html">
-      <meta property="docfx:tocrel" content="../../toc.html">
-    
-    <meta property="docfx:rel" content="../../../">
-    
-  </head>
-  <body data-spy="scroll" data-target="#affix" data-offset="120">
-    <div id="wrapper">
-      <header>        
-
-        <nav id="autocollapse" class="navbar navbar-inverse ng-scope" role="navigation">
-          <div class="container">
-            <div class="navbar-header">
-              <button type="button" class="navbar-toggle" data-toggle="collapse" data-target="#navbar">
-                <span class="sr-only">Toggle navigation</span>
-                <span class="icon-bar"></span>
-                <span class="icon-bar"></span>
-                <span class="icon-bar"></span>
-              </button>
-
-              <a class="navbar-brand" href="https://developers.rws.com/">
-                <img id="logo" class="svg" src="../../../logo.svg" alt="">
-              </a>
-            </div>
-            <div class="collapse navbar-collapse" id="navbar">
-              <form class="navbar-form navbar-right" role="search" id="search">
-                <div class="form-group">
-                  <span class="glyphicon glyphicon-search search-icon"></span>
-                  <input type="text" class="form-control" id="search-query" placeholder="Search" autocomplete="off">
-                </div>
-              </form>
-            </div>
-          </div>
-        </nav>
-
-        <div class="subnav navbar navbar-default">
-          <div class="container hide-when-search" id="breadcrumb">
-            <ul class="breadcrumb">
-              <li></li>
-            </ul>
-          </div>
-        </div>
-      </header>
-
-        <div class="container body-content">
-
-          <div id="search-results">
-            <div class="search-list">Search Results for <span></span></div>
-            <div class="sr-items">
-              <p><i class="glyphicon glyphicon-refresh index-loading"></i></p>
-            </div>
-            <ul id="pagination" data-first=First data-prev=Previous data-next=Next data-last=Last></ul>
-          </div>
-        </div>
-
-      <div role="main" class="container body-content hide-when-search">
-
-        <div class="sidenav hide-when-search">
-          <a class="btn toc-toggle collapse" data-toggle="collapse" href="#sidetoggle" aria-expanded="false" aria-controls="sidetoggle">Show / Hide Table of Contents</a>
-          <div class="sidetoggle collapse" id="sidetoggle">
-            <div id="sidetoc"></div>
-          </div>
-        </div>
-        <div class="article row grid-right">
-          <div class="col-md-10">
-            <article class="content wrap" id="_content" data-uid="">
-<h1 id="how-to-update-plugins-to-trados-studio-2024">How to update plugins to Trados Studio 2024</h1>
-
-<p>The following are a list of changes and known issues to consider when updating your plugin to be compatible with Trados Studio 2024.</p>
-<h2 id="plugin-framework">Plugin Framework</h2>
-<p>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.</p>
-<h3 id="package-manager-ui">Package Manager UI</h3>
-<ul>
-<li>In <strong>Solution Explorer</strong>, right-click <strong>References</strong> and choose <strong>Manage NuGet Packages</strong>.</li>
-<li>Select nuget.org as the <strong>Package source</strong>.</li>
-<li>Search for <code>Sdl.Core.PluginFramework</code> from the <strong>Browse</strong> tab.</li>
-<li>Select the package from the list and click <strong>Install</strong> or <strong>Update</strong>.
-<ul>
-<li><code>Sdl.Core.PluginFramework</code>, version <em>2.1.0</em></li>
-<li><code>Sdl.Core.PluginFramework.Build</code>, version <em>18.0.1</em></li>
-</ul>
-</li>
-<li>Accept any license prompts to finnish the installation.</li>
-</ul>
-<br>
-<h2 id="plugin-manifest">Plugin Manifest</h2>
-<p>The manifest file <strong>pluginpackage.manifest.xml</strong> is located at the root of your project solution.  The values of the <strong>RequiredProduct</strong> should be updated to align with the latest release.</p>
-<h3 id="requiredproduct">RequiredProduct</h3>
-<ul>
-<li>Min version should be set to: 18.0.</li>
-<li>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.</li>
-<li>Name should be set to: <em>TradosStudio</em></li>
-</ul>
-<p>Example</p>
-<pre><code class="lang-xml">&lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot;?&gt;
-&lt;PluginPackage xmlns=&quot;http://www.sdl.com/Plugins/PluginPackage/1.0&quot;&gt;
-  &lt;PlugInName&gt;My plugin name&lt;/PlugInName&gt;
-  &lt;Version&gt;1.1.0.0&lt;/Version&gt;
-  &lt;Description&gt;My plugin description&lt;/Description&gt;
-  &lt;Author&gt;Trados AppStore Team&lt;/Author&gt;
-  &lt;RequiredProduct name=&quot;TradosStudio&quot; minversion=&quot;18.0&quot; maxversion=&quot;18.9&quot; /&gt;
-&lt;/PluginPackage&gt;
-</code></pre>
-<h2 id="project-references--deployment-path">Project References &amp; Deployment Path</h2>
-<p>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.</p>
-<div class="tabGroup" id="tabgroup_1">
-<ul role="tablist">
-<li role="presentation">
-<a href="#tabpanel_1_standard" role="tab" aria-controls="tabpanel_1_standard" data-tab="standard" tabindex="0" aria-selected="true">Production</a>
-</li>
-<li role="presentation">
-<a href="#tabpanel_1_beta" role="tab" aria-controls="tabpanel_1_beta" data-tab="beta" tabindex="-1">BETA</a>
-</li>
-</ul>
-<section id="tabpanel_1_standard" role="tabpanel" data-tab="standard">
-
-<p>Installation path: <em>$(MSBuildProgramFiles32)\Trados\Trados Studio\Studio18</em>:</p>
-<pre><code class="lang-xml">&lt;Reference Include=&quot;Sdl.Desktop.IntegrationApi.Extensions&quot;&gt;
-    &lt;HintPath&gt;$(MSBuildProgramFiles32)\Trados\Trados Studio\Studio18\Sdl.Desktop.IntegrationApi.Extensions.dll&lt;/HintPath&gt;
-&lt;/Reference&gt;
-</code></pre>
-<br>
-<p>Plugin deployment path: <em>$(AppData)\Trados\Trados Studio\18\Plugins</em>:</p>
-<pre><code class="lang-xml">&lt;PluginDeploymentPath&gt;$(AppData)\Trados\Trados Studio\18\Plugins&lt;/PluginDeploymentPath&gt;
-</code></pre>
-</section>
-<section id="tabpanel_1_beta" role="tabpanel" data-tab="beta" aria-hidden="true" hidden="hidden">
-
-<p>Installation path: <em>$(MSBuildProgramFiles32)\Trados\Trados Studio\Studio18Beta</em>:</p>
-<pre><code class="lang-xml">&lt;Reference Include=&quot;Sdl.Desktop.IntegrationApi.Extensions&quot;&gt;
-    &lt;HintPath&gt;$(MSBuildProgramFiles32)\Trados\Trados Studio\Studio18Beta\Sdl.Desktop.IntegrationApi.Extensions.dll&lt;/HintPath&gt;
-&lt;/Reference&gt;
-</code></pre>
-<br>
-<p>Plugin deployment path: <em>$(AppData)\Trados\Trados Studio\18Beta\Plugins</em>:</p>
-<pre><code class="lang-xml">&lt;PluginDeploymentPath&gt;$(AppData)\Trados\Trados Studio\18Beta\Plugins&lt;/PluginDeploymentPath&gt;
-</code></pre>
-</section>
-</div>
-
-<div class="NOTE">
-<h5>Note</h5>
-<p>To update settings directly in the project file from Visual Studio</p>
-<ul>
-<li>Right-click on the project node in the <strong>Solution Explorer</strong> and select <strong>Unload Project</strong>.</li>
-<li>Then, right-click on the project and choose <strong>Edit</strong> <projectname></projectname></li>
-</ul>
-<p>Once you have applied your changes in the project file, then reload project</p>
-<ul>
-<li>In the <strong>Solution Explorer</strong>, select the projects you want to load (press <strong>Ctrl</strong> while clicking to select more than one project)</li>
-<li>Then right-click on the project and choose <strong>Reload Project</strong>.</li>
-</ul>
-</div>
-<br>
-<br>
-<h2 id="known-issues">Known Issues</h2>
-<p>The following are a list of known issues and solutions that you might encounter depending on your settings and configuration:</p>
-<h3 id="tradoscommunitytoolkit-formally-sdlcommunitytoolkit">Trados.Community.Toolkit (formally SDL.Community.Toolkit)</h3>
-<p>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:</p>
-<ul>
-<li><a href="https://www.nuget.org/packages/Trados.Community.Toolkit.Core">Trados.Community.Toolkit.Core</a></li>
-<li><a href="https://www.nuget.org/packages/Trados.Community.Toolkit.LanguagePlatform">Trados.Community.Toolkit.LanguagePlatform</a></li>
-<li><a href="https://www.nuget.org/packages/Trados.Community.Toolkit.Integration">Trados.Community.Toolkit.Integration</a></li>
-<li><a href="https://www.nuget.org/packages/Trados.Community.Toolkit.FileType">Trados.Community.Toolkit.FileType</a></li>
-<li><a href="https://www.nuget.org/packages/Trados.Community.Toolkit.ProjectAutomation">Trados.Community.Toolkit.ProjectAutomation</a></li>
-</ul>
-<h3 id="dependency-version-changes">Dependency version changes</h3>
-<p>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.</p>
-<pre><code class="lang-xml">&lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot; ?&gt;
-&lt;configuration&gt;
-  &lt;startup&gt;
-    &lt;supportedRuntime version=&quot;v4.0&quot; sku=&quot;.NETFramework,Version=v4.8&quot; /&gt;
-  &lt;/startup&gt;
-  &lt;runtime&gt;
-    &lt;NetFx40_PInvokeStackResilience enabled=&quot;1&quot; /&gt;
-    &lt;legacyCorruptedStateExceptionsPolicy enabled=&quot;true&quot; /&gt;
-    &lt;ThrowUnobservedTaskException enabled=&quot;true&quot; /&gt;
-    &lt;assemblyBinding xmlns=&quot;urn:schemas-microsoft-com:asm.v1&quot;&gt;
-      &lt;dependentAssembly&gt;
-        &lt;assemblyIdentity name=&quot;Microsoft.Extensions.DependencyModel&quot; publicKeyToken=&quot;adb9793829ddae60&quot; culture=&quot;neutral&quot; /&gt;
-        &lt;bindingRedirect oldVersion=&quot;0.0.0.0-7.0.0.0&quot; newVersion=&quot;7.0.0.0&quot; /&gt;
-      &lt;/dependentAssembly&gt;
-    &lt;/assemblyBinding&gt;
-  &lt;/runtime&gt;
-&lt;/configuration&gt;
-</code></pre>
-
-</article>
-          </div>
-
-          <div class="hidden-sm col-md-2" role="complementary">
-            <div class="sideaffix">
-              <div class="contribution">
-                <ul class="nav">
-                  <li>
-                    <a href="https://github.com/RWS/studio-api-docs/blob/main/articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2024.md/#L1" class="contribution-link">Improve this Doc</a>
-                  </li>
-                </ul>
-              </div>
-              <nav class="bs-docs-sidebar hidden-print hidden-xs hidden-sm affix" id="affix">
-                <h5>In this article</h5>
-                <div></div>
-              </nav>
-            </div>
-          </div>
-        </div>
-      </div>
-
-      <footer>
-        <div class="grad-bottom"></div>
-        <div class="footer">
-          <div class="container">
-            <span class="pull-right">
-              <a href="#top">Back to top</a>
-            </span>
-      
-      <span>Generated by <strong>DocFX</strong></span>
-          </div>
-        </div>
-      </footer>
-    </div>
-
-    <script type="text/javascript" src="../../../styles/docfx.vendor.min.js"></script>
-    <script type="text/javascript" src="../../../styles/docfx.js"></script>
-    <script type="text/javascript" src="../../../styles/main.js"></script>
-  </body>
-</html>
\ No newline at end of file
diff --git a/articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2024_sr1.html b/articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2026.html
similarity index 70%
rename from articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2024_sr1.html
rename to articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2026.html
index 71f7f7140..b07dce99b 100644
--- a/articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2024_sr1.html
+++ b/articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2026.html
@@ -5,9 +5,9 @@
   <head>
     <meta charset="utf-8">
       <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
-      <title>How to update plugins to Trados Studio 2024 SR1 </title>
+      <title>How to update plugins to Trados Studio 2026 Release </title>
       <meta name="viewport" content="width=device-width">
-      <meta name="title" content="How to update plugins to Trados Studio 2024 SR1 ">
+      <meta name="title" content="How to update plugins to Trados Studio 2026 Release ">
     
     
       <link rel="shortcut icon" href="../../../favicon.ico">
@@ -80,9 +80,22 @@
         <div class="article row grid-right">
           <div class="col-md-10">
             <article class="content wrap" id="_content" data-uid="">
-<h1 id="how-to-update-plugins-to-trados-studio-2024-sr1">How to update plugins to Trados Studio 2024 SR1</h1>
+<h1 id="how-to-update-plugins-to-trados-studio-2026-release">How to update plugins to Trados Studio 2026 Release</h1>
 
-<p>The following are a list of changes and known issues to consider when updating your plugin to be compatible with Trados Studio 2024 SR1.</p>
+<p>The following are a list of changes and known issues to consider when updating your plugin to be compatible with Trados Studio 2026 Release.</p>
+<h2 id="transition-to-64-bit-x64">Transition to 64-Bit (x64)</h2>
+<p>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.</p>
+<p>The following element must be added in a global property group of the .csproj file to target x64:</p>
+<pre><code class="lang-xml">&lt;PropertyGroup&gt;
+	...
+	&lt;PlatformTarget&gt;x64&lt;/PlatformTarget&gt;
+	...
+&lt;/PropertyGroup&gt;
+</code></pre>
+<div class="NOTE">
+<h5>Note</h5>
+<p>If the project is not SDK-style, <platformtarget>x64</platformtarget> must be set for all relevant configurations (e.g., Debug and Release), otherwise some builds may still compile for a different platform.</p>
+</div>
 <h2 id="update-plugin-framework-packages">Update Plugin Framework Packages</h2>
 <p>Ensure you are using the latest plugin framework NuGet packages:</p>
 <ul>
@@ -101,13 +114,13 @@ <h2 id="update-plugin-manifest">Update Plugin Manifest</h2>
 <pre><code class="lang-xml">&lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot;?&gt;
 &lt;PluginPackage xmlns=&quot;http://www.sdl.com/Plugins/PluginPackage/1.0&quot;&gt;
   &lt;PlugInName&gt;My plugin name&lt;/PlugInName&gt;
-  &lt;Version&gt;1.1.0.0&lt;/Version&gt;
+  &lt;Version&gt;1.0.0.0&lt;/Version&gt;
   &lt;Description&gt;My plugin description&lt;/Description&gt;
   &lt;Author&gt;Trados AppStore Team&lt;/Author&gt;
-  &lt;RequiredProduct name=&quot;TradosStudio&quot; minversion=&quot;18.1&quot; maxversion=&quot;18.1.9&quot; /&gt;
+  &lt;RequiredProduct name=&quot;TradosStudio&quot; minversion=&quot;19.0&quot; maxversion=&quot;19.9&quot; /&gt;
 &lt;/PluginPackage&gt;
 </code></pre>
-<p>Ensure <strong>RequiredProduct</strong> reflects <code>minversion=&quot;18.1&quot;</code> and <code>maxversion=&quot;18.1.9&quot;</code>.</p>
+<p>Ensure <strong>RequiredProduct</strong> reflects <code>minversion=&quot;19.0&quot;</code> and <code>maxversion=&quot;19.9&quot;</code>.</p>
 <h2 id="project-references--deployment-path">Project References &amp; Deployment Path</h2>
 <p>Update references and deployment settings in your .csproj:</p>
 <div class="tabGroup" id="tabgroup_1">
@@ -121,24 +134,24 @@ <h2 id="project-references--deployment-path">Project References &amp; Deployment
 </ul>
 <section id="tabpanel_1_standard" role="tabpanel" data-tab="standard">
 
-<p><strong>References</strong>: Set Trados Studio assemblies to use the Studio 18 path:</p>
+<p><strong>References</strong>: Set Trados Studio assemblies to use the Studio 19 path:</p>
 <pre><code class="lang-xml">&lt;Reference Include=&quot;Sdl.Desktop.IntegrationApi.Extensions&quot;&gt;
-    &lt;HintPath&gt;$(MSBuildProgramFiles32)\Trados\Trados Studio\Studio18\Sdl.Desktop.IntegrationApi.Extensions.dll&lt;/HintPath&gt;
+    &lt;HintPath&gt;$(ProgramFiles)\Trados\Trados Studio\Studio19\Sdl.Desktop.IntegrationApi.Extensions.dll&lt;/HintPath&gt;
 &lt;/Reference&gt;
 </code></pre>
 <p><strong>Deployment Path:</strong></p>
-<pre><code class="lang-xml">&lt;PluginDeploymentPath&gt;$(AppData)\Trados\Trados Studio\18\Plugins&lt;/PluginDeploymentPath&gt;
+<pre><code class="lang-xml">&lt;PluginDeploymentPath&gt;$(AppData)\Trados\Trados Studio\19\Plugins&lt;/PluginDeploymentPath&gt;
 </code></pre>
 </section>
 <section id="tabpanel_1_beta" role="tabpanel" data-tab="beta" aria-hidden="true" hidden="hidden">
 
-<p><strong>References</strong>: Set Trados Studio assemblies to use the Studio 18 Beta path:</p>
+<p><strong>References</strong>: Set Trados Studio assemblies to use the Studio 19 Beta path:</p>
 <pre><code class="lang-xml">&lt;Reference Include=&quot;Sdl.Desktop.IntegrationApi.Extensions&quot;&gt;
-    &lt;HintPath&gt;$(MSBuildProgramFiles32)\Trados\Trados Studio\Studio18Beta\Sdl.Desktop.IntegrationApi.Extensions.dll&lt;/HintPath&gt;
+    &lt;HintPath&gt;$(ProgramFiles)\Trados\Trados Studio\Studio19Beta\Sdl.Desktop.IntegrationApi.Extensions.dll&lt;/HintPath&gt;
 &lt;/Reference&gt;
 </code></pre>
 <p><strong>Deployment Path:</strong></p>
-<pre><code class="lang-xml">&lt;PluginDeploymentPath&gt;$(AppData)\Trados\Trados Studio\18Beta\Plugins&lt;/PluginDeploymentPath&gt;
+<pre><code class="lang-xml">&lt;PluginDeploymentPath&gt;$(AppData)\Trados\Trados Studio\19Beta\Plugins&lt;/PluginDeploymentPath&gt;
 </code></pre>
 </section>
 </div>
@@ -155,10 +168,11 @@ <h5>Note</h5>
 <li>In the <strong>Solution Explorer</strong>, select the projects you want to load (press <strong>Ctrl</strong> while clicking to select more than one project)</li>
 <li>Then right-click on the project and choose <strong>Reload Project</strong>.</li>
 </ul>
+<p>If the project is SDK-style, then unloading/reloading is unnecessary.</p>
 </div>
-<br>
 <h2 id="known-issues--dependency-updates">Known Issues &amp; Dependency Updates</h2>
-<h3 id="dependency-version-changes">Dependency Version Changes</h3>
+<p>The following are a list of known issues and solutions that you might encounter depending on your settings and configuration:</p>
+<h3 id="dependency-version-changes">Dependency version changes</h3>
 <p>Standalone integrations may require binding redirects. Example for <code>App.config</code>:</p>
 <pre><code class="lang-xml">&lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot; ?&gt;
 &lt;configuration&gt;
@@ -193,11 +207,25 @@ <h3 id="dependency-version-changes">Dependency Version Changes</h3>
   &lt;/startup&gt;  
 &lt;/configuration&gt;
 </code></pre>
-<br>
-<h2 id="breaking-api-changes">Breaking API Changes</h2>
-<h3 id="assembly-version-change-requires-recompilation">Assembly Version Change Requires Recompilation</h3>
-<p>With Trados Studio 2024 SR1, all core Trados assemblies have had their <strong>assembly version increased to 18.1.x.x</strong> (reflecting the semantic versioning minor update). <strong>This assembly version bump introduces a breaking change:</strong> 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.<br>
-<br></p>
+<h3 id="breaking-api-changes">Breaking API Changes</h3>
+<p><code>ITerminologyProviderCredentialStore</code> was removed (together with method parameters of this type).</p>
+<p><code>TerminologyProviderManager.DefaultTerminologyCredentialStore</code> was removed.</p>
+<p><code>public TerminologyProviderType Type</code> property removed from <code>ITerminologyProvider</code></p>
+<h4 id="working-with-bcms">Working with BCMs</h4>
+<p>The BCM-related classes have been moved from Sdl.LanguagePlatform.TranslationMemoryApito TradosStudio.BcmLite:</p>
+<pre><code class="lang-xml">&lt;Reference Include=&quot;TradosStudio.BcmLite&quot;&gt;
+	&lt;HintPath&gt;$(ProgramFiles)\Trados\Trados Studio\Studio19\TradosStudio.BcmLite.dll&lt;/HintPath&gt;
+&lt;/Reference&gt;
+</code></pre>
+<p>And some classes were renamed:</p>
+<p><code>LiteDocument</code> to <code>Document</code></p>
+<p><code>LiteFragment</code> to <code>DocumentFragment</code></p>
+<p>The <code>LiteBcmVisitor</code> abstract class now includes two more methods:</p>
+<pre><code class="lang-cs">public abstract void VisitFeedbackContainer(FeedbackContainer feedbackContainer);
+public abstract void VisitStructure(StructureTag structureTag);
+</code></pre>
+<h4 id="assembly-version-change-requires-recompilation">Assembly Version Change Requires Recompilation</h4>
+<p>With Trados Studio 2026 Release, all core Trados assemblies have had their <strong>assembly version increased to 19.x.x.x</strong> (reflecting the semantic versioning minor update). <strong>This assembly version bump introduces a breaking change:</strong> 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.</p>
 <h3 id="multiterm-api-changes">Multiterm API Changes</h3>
 <p><strong>Migrate from <code>Sdl.Multiterm.TMO.Interop.dll</code> to <code>TerminologyProviderManager</code></strong></p>
 <p>As part of the separation of MultiTerm from Trados Studio, the legacy assembly <code>Sdl.Multiterm.TMO.Interop.dll</code> <strong>has been removed from the Trados Studio installation folder as of SR1</strong>. Any integration or plugin referencing TMO interop must be updated: <strong>the endorsed approach for terminology-related integrations moving forward is the <code>TerminologyProviderManager</code> singleton.</strong></p>
@@ -206,7 +234,7 @@ <h3 id="multiterm-api-changes">Multiterm API Changes</h3>
 <pre><code class="lang-csharp">using Sdl.Terminology.TerminologyProvider.Core;
 
 // Example URI for your termbase
-string termbaseUriString = &quot;file:///C:/Termbases/MyTermbase.sdltb&quot;;
+string termbaseUriString = &quot;ttb.file:///C:/Termbases/MyTermbase.ttb&quot;;
 Uri termbaseUri = new Uri(termbaseUriString);
 
 // Get the terminology provider singleton instance
@@ -227,8 +255,16 @@ <h3 id="multiterm-api-changes">Multiterm API Changes</h3>
 }
 
 // Set up search parameters
-var sourceLanguage = new CultureInfo(&quot;en-US&quot;);
-var targetLanguage = new CultureInfo(&quot;it-IT&quot;);
+var sourceLanguage = new DefinitionLanguage
+{
+    Locale = &quot;EN&quot;,
+    Name = &quot;English&quot;
+};
+var targetLanguage = new DefinitionLanguage
+{
+    Locale = &quot;DE&quot;,
+    Name = &quot;German&quot;
+};
 string segmentText = &quot;Insert your source segment text here&quot;;
 int maxResultsCount = 10;
 bool targetRequired = true;
@@ -245,77 +281,16 @@ <h3 id="multiterm-api-changes">Multiterm API Changes</h3>
 
 // Process or display results as needed...
 </code></pre>
-<p><strong>Note:</strong> Replace any references to <code>Sdl.Multiterm.TMO.Interop.dll</code> with the modern <code>TerminologyProviderManager</code> API. This ensures compatibility with Trados Studio 2024 SR1 and future releases, and aligns with Trados ongoing architectural updates.</p>
-<br>
-<h2 id="credential-management-best-practices">Credential Management Best Practices</h2>
-<p>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.</p>
-<p><strong>Key Points:</strong></p>
+<p><strong>Note:</strong> Replace any references to <code>Sdl.Multiterm.TMO.Interop.dll</code> with the modern <code>TerminologyProviderManager</code> API. This ensures compatibility with Trados Studio 2026 Release and future releases, and aligns with Trados ongoing architectural updates.</p>
+<h3 id="tradoscommunitytoolkit-formally-sdlcommunitytoolkit">Trados.Community.Toolkit (formally SDL.Community.Toolkit)</h3>
+<p>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:</p>
 <ul>
-<li>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).</li>
-<li>For all other scenarios, including any third-party or custom service integration, you should implement your own secure mechanism for storing and retrieving credentials.</li>
-<li>Managing credentials independently enhances security and gives you greater flexibility and control.</li>
+<li><a href="https://www.nuget.org/packages/Trados.Community.Toolkit.Core">Trados.Community.Toolkit.Core</a></li>
+<li><a href="https://www.nuget.org/packages/Trados.Community.Toolkit.LanguagePlatform">Trados.Community.Toolkit.LanguagePlatform</a></li>
+<li><a href="https://www.nuget.org/packages/Trados.Community.Toolkit.Integration">Trados.Community.Toolkit.Integration</a></li>
+<li><a href="https://www.nuget.org/packages/Trados.Community.Toolkit.FileType">Trados.Community.Toolkit.FileType</a></li>
+<li><a href="https://www.nuget.org/packages/Trados.Community.Toolkit.ProjectAutomation">Trados.Community.Toolkit.ProjectAutomation</a></li>
 </ul>
-<p><strong>Best Practice:</strong>
-Always use your own secure credential management system, unless your integration specifically requires direct access to Trados resources.</p>
-<hr>
-<h3 id="example-managing-credentials-securely">Example: Managing Credentials Securely</h3>
-<p>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.</p>
-<p><strong>Credential Store Interface:</strong></p>
-<pre><code class="lang-csharp">public interface ICredentialStore
-{
-    void SaveCredential(string key, string username, string password);
-    (string Username, string Password)? GetCredential(string key);
-    void RemoveCredential(string key);
-}
-</code></pre>
-<p><strong>Sample Windows Credential Manager Implementation</strong><br>
-<em>Install the <a href="https://www.nuget.org/packages/CredentialManagement/">CredentialManagement</a> NuGet package for this sample:</em></p>
-<pre><code class="lang-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();
-    }
-}
-</code></pre>
-<p><strong>How to Use in Your Integration</strong></p>
-<pre><code class="lang-csharp">// Example usage
-var credentialStore = new WindowsCredentialStore();
-var credentials = credentialStore.GetCredential(&quot;your-provider-key&quot;);
-if (credentials.HasValue) {
-    var username = credentials.Value.Username;
-    var password = credentials.Value.Password;
-    // Use credentials securely...
-} else {
-    // Handle missing credentials scenario
-}
-</code></pre>
-<p><strong>Note:</strong> Using your own credential store ensures future compatibility, enhances security, and keeps your integration flexible as Trados Studio and its APIs evolve.</p>
 
 </article>
           </div>
@@ -325,7 +300,7 @@ <h3 id="example-managing-credentials-securely">Example: Managing Credentials Sec
               <div class="contribution">
                 <ul class="nav">
                   <li>
-                    <a href="https://github.com/RWS/studio-api-docs/blob/main/articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2024_sr1.md/#L1" class="contribution-link">Improve this Doc</a>
+                    <a href="https://github.com/RWS/studio-api-docs/blob/main/articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2026.md/#L1" class="contribution-link">Improve this Doc</a>
                   </li>
                 </ul>
               </div>
diff --git a/articles/toc.html b/articles/toc.html
index 9399d36b9..f3474557a 100644
--- a/articles/toc.html
+++ b/articles/toc.html
@@ -55,10 +55,7 @@
                               <a href="hints_tips/Studio_Styles/StudioStyles.html" name="" title="Studio Look &amp; Feel in your 3rd party plugin">Studio Look &amp; Feel in your 3rd party plugin</a>
                           </li>
                           <li>
-                              <a href="hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2024.html" name="" title="How to update plugins to Trados Studio 2024">How to update plugins to Trados Studio 2024</a>
-                          </li>
-                          <li>
-                              <a href="hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2024_sr1.html" name="" title="How to update plugins to Trados Studio 2024 SR1">How to update plugins to Trados Studio 2024 SR1</a>
+                              <a href="hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2026.html" name="" title="How to update plugins to Trados Studio 2026 Release">How to update plugins to Trados Studio 2026 Release</a>
                           </li>
                           <li>
                               <a href="hints_tips/UsefulTips/UsefulTipsApiArticle.html" name="" title="How to implement the Studio Useful Tips service">How to implement the Studio Useful Tips service</a>
diff --git a/articles/toc.json b/articles/toc.json
index 03e0e0b96..acc5ad950 100644
--- a/articles/toc.json
+++ b/articles/toc.json
@@ -1,2 +1,2 @@
 
-{"items":[{"name":"Introduction","href":"intro.html","topicHref":"intro.html"},{"name":"Getting Started","href":"gettingstarted/studio_plugin_overview.html","topicHref":"gettingstarted/studio_plugin_overview.html","items":[{"name":"Trados Studio plug-in overview","href":"gettingstarted/studio_plugin_overview.html","topicHref":"gettingstarted/studio_plugin_overview.html"},{"name":"Platform support","href":"gettingstarted/platform_support.html","topicHref":"gettingstarted/platform_support.html"},{"name":"Setting up a Developer Machine","href":"gettingstarted/setting_up_a_developer_machine.html","topicHref":"gettingstarted/setting_up_a_developer_machine.html"},{"name":"Building a plug-in","href":"gettingstarted/building_a_plugin.html","topicHref":"gettingstarted/building_a_plugin.html"},{"name":"Plug-in deployment","href":"gettingstarted/plugin_deployment.html","topicHref":"gettingstarted/plugin_deployment.html"},{"name":"Plugin use-cases","href":"gettingstarted/plugin_use_cases.html","topicHref":"gettingstarted/plugin_use_cases.html"},{"name":"Community Plugins","href":"gettingstarted/community_plugins.html","topicHref":"gettingstarted/community_plugins.html"}]},{"name":"Hints & Tips","href":"hints_tips/hints_tips_overview.html","topicHref":"hints_tips/hints_tips_overview.html","items":[{"name":"Better Studio interactivity in day to day flows","href":"hints_tips/Better_Studio_interactivity/SR2ApiArticle.html","topicHref":"hints_tips/Better_Studio_interactivity/SR2ApiArticle.html"},{"name":"Studio Look & Feel in your 3rd party plugin","href":"hints_tips/Studio_Styles/StudioStyles.html","topicHref":"hints_tips/Studio_Styles/StudioStyles.html"},{"name":"How to update plugins to Trados Studio 2024","href":"hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2024.html","topicHref":"hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2024.html"},{"name":"How to update plugins to Trados Studio 2024 SR1","href":"hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2024_sr1.html","topicHref":"hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2024_sr1.html"},{"name":"How to implement the Studio Useful Tips service","href":"hints_tips/UsefulTips/UsefulTipsApiArticle.html","topicHref":"hints_tips/UsefulTips/UsefulTipsApiArticle.html"},{"name":"How to implement an AI Companion","href":"hints_tips/AI_Companion/AICompanion.html","topicHref":"hints_tips/AI_Companion/AICompanion.html"}]}]}
+{"items":[{"name":"Introduction","href":"intro.html","topicHref":"intro.html"},{"name":"Getting Started","href":"gettingstarted/studio_plugin_overview.html","topicHref":"gettingstarted/studio_plugin_overview.html","items":[{"name":"Trados Studio plug-in overview","href":"gettingstarted/studio_plugin_overview.html","topicHref":"gettingstarted/studio_plugin_overview.html"},{"name":"Platform support","href":"gettingstarted/platform_support.html","topicHref":"gettingstarted/platform_support.html"},{"name":"Setting up a Developer Machine","href":"gettingstarted/setting_up_a_developer_machine.html","topicHref":"gettingstarted/setting_up_a_developer_machine.html"},{"name":"Building a plug-in","href":"gettingstarted/building_a_plugin.html","topicHref":"gettingstarted/building_a_plugin.html"},{"name":"Plug-in deployment","href":"gettingstarted/plugin_deployment.html","topicHref":"gettingstarted/plugin_deployment.html"},{"name":"Plugin use-cases","href":"gettingstarted/plugin_use_cases.html","topicHref":"gettingstarted/plugin_use_cases.html"},{"name":"Community Plugins","href":"gettingstarted/community_plugins.html","topicHref":"gettingstarted/community_plugins.html"}]},{"name":"Hints & Tips","href":"hints_tips/hints_tips_overview.html","topicHref":"hints_tips/hints_tips_overview.html","items":[{"name":"Better Studio interactivity in day to day flows","href":"hints_tips/Better_Studio_interactivity/SR2ApiArticle.html","topicHref":"hints_tips/Better_Studio_interactivity/SR2ApiArticle.html"},{"name":"Studio Look & Feel in your 3rd party plugin","href":"hints_tips/Studio_Styles/StudioStyles.html","topicHref":"hints_tips/Studio_Styles/StudioStyles.html"},{"name":"How to update plugins to Trados Studio 2026 Release","href":"hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2026.html","topicHref":"hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2026.html"},{"name":"How to implement the Studio Useful Tips service","href":"hints_tips/UsefulTips/UsefulTipsApiArticle.html","topicHref":"hints_tips/UsefulTips/UsefulTipsApiArticle.html"},{"name":"How to implement an AI Companion","href":"hints_tips/AI_Companion/AICompanion.html","topicHref":"hints_tips/AI_Companion/AICompanion.html"}]}]}
diff --git a/index.html b/index.html
index 87028d3dd..3e07307a4 100644
--- a/index.html
+++ b/index.html
@@ -5,9 +5,9 @@
   <head>
     <meta charset="utf-8">
       <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
-      <title>Access the Trados Studio 2024 SR1 APIs </title>
+      <title>Access the Trados Studio 2026 Release APIs </title>
       <meta name="viewport" content="width=device-width">
-      <meta name="title" content="Access the Trados Studio 2024 SR1 APIs ">
+      <meta name="title" content="Access the Trados Studio 2026 Release APIs ">
     
     
       <link rel="shortcut icon" href="favicon.ico">
@@ -73,14 +73,14 @@
         <div class="article row grid">
           <div class="col-md-10">
             <article class="content wrap" id="_content" data-uid="">
-<h1 id="access-the-varproductnamewithedition-apis">Access the Trados Studio 2024 SR1 APIs</h1>
+<h1 id="access-the-varproductnamewithedition-apis">Access the Trados Studio 2026 Release APIs</h1>
 
-<h2 id="getting-started-with-varproductnamewithedition-apis"><a href="articles/gettingstarted/studio_plugin_overview.html">Getting started with Trados Studio 2024 SR1 APIs</a></h2>
+<h2 id="getting-started-with-varproductnamewithedition-apis"><a href="articles/gettingstarted/studio_plugin_overview.html">Getting started with Trados Studio 2026 Release APIs</a></h2>
 <p>Read more on how you can write your first Trados Studio plugin.</p>
-<h2 id="learn-more-about-varproductnamewithedition-apis"><a href="apiconcepts/overview.html">Learn more about Trados Studio 2024 SR1 APIs</a></h2>
+<h2 id="learn-more-about-varproductnamewithedition-apis"><a href="apiconcepts/overview.html">Learn more about Trados Studio 2026 Release APIs</a></h2>
 <p>Learn more about the APIs and what you can achieve with them.</p>
-<h2 id="how-to-update-plugins-to-varproductnamewithedition"><a href="articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2024.html">How to update plugins to Trados Studio 2024 SR1</a></h2>
-<p>Learn more about how you can make your plugin compatible with Trados Studio 2024 SR1.</p>
+<h2 id="how-to-update-plugins-to-varproductnamewithedition"><a href="articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2024.md">How to update plugins to Trados Studio 2026 Release</a></h2>
+<p>Learn more about how you can make your plugin compatible with Trados Studio 2026 Release.</p>
 <h2 id="articles"><a href="articles/intro.html">Articles</a></h2>
 <p>Read articles on how to get more out of Trados Studio.</p>
 <h2 id="code-samples"><a href="https://github.com/RWS/trados-studio-api-samples">Code samples</a></h2>
@@ -88,6 +88,7 @@ <h2 id="code-samples"><a href="https://github.com/RWS/trados-studio-api-samples"
 <h2 id="open-source-community-projects"><a href="https://github.com/RWS/Sdl-Community">Open Source Community Projects</a></h2>
 <p>Join our community-driven repository of Trados Studio plugins on <a href="https://github.com/RWS/Sdl-Community">RWS Community</a>.</p>
 <h2 id="varproductname-api-versions">Trados Studio API versions</h2>
+<h3 id="varproductname-2024-sr1---api-181"><a href="http://developers.rws.com/studio-api-docs/18.1/index.html">Trados Studio 2024 SR1 - API 18.1</a></h3>
 <h3 id="varproductname-2024---api-180"><a href="http://developers.rws.com/studio-api-docs/18.0/index.html">Trados Studio 2024 - API 18.0</a></h3>
 <h3 id="varproductname-2022---api-172"><a href="http://developers.rws.com/studio-api-docs/17.2/index.html">Trados Studio 2022 - API 17.2</a></h3>
 <h3 id="varproductname-2022---api-171"><a href="http://developers.rws.com/studio-api-docs/17.1/index.html">Trados Studio 2022 - API 17.1</a></h3>
diff --git a/index.json b/index.json
index a685095b2..58944e56b 100644
--- a/index.json
+++ b/index.json
@@ -10979,15 +10979,10 @@
     "title": "Studio Look & Feel in your 3rd party plugin",
     "summary": "Studio Look & Feel in your 3rd party plugin Together with the release of Var:ProductName 2019 SR2 two new APIs were exposed which will allows you to take advantage of Studio styles in your plugin: Sdl.Desktop.Platform.Styles.dll Sdl.Desktop.Platform.Controls.dll Note In order to use Studio styles your plugin must be written in WPF. Sample application can be found in public AppStore Community repository on GitHub. Throughout this article we will be presenting some Studio styles and controls and how you can use them in your application. Sdl.Desktop.Platform.Styles.dll In this API were released following Studio resources: Buttons Checkbox Combobox DataGrid Generic Error style Groupbox NumericUpDown Progress Ring (Asterisk) Radio Button TextBlock TextBox TreeView How to use resource styles in your plugin? First of all you have to import all the .xaml files you want to use in your application: <ResourceDictionary> <ResourceDictionary.MergedDictionaries> <ResourceDictionary Source=\"/Sdl.Desktop.Platform.Styles;component/ButtonResources.xaml\"/> <ResourceDictionary Source=\"/Sdl.Desktop.Platform.Styles;component/TextBoxResources.xaml\"/> <ResourceDictionary Source=\"/Sdl.Desktop.Platform.Styles;component/TextBlockResources.xaml\"/> <ResourceDictionary Source=\"/Sdl.Desktop.Platform.Styles;component/GroupboxResources.xaml\"/> <ResourceDictionary Source=\"/Sdl.Desktop.Platform.Styles;component/DataGridResources.xaml\"/> <ResourceDictionary Source=\"/Sdl.Desktop.Platform.Styles;component/NumericUpDown.xaml\"/> <ResourceDictionary Source=\"/Sdl.Desktop.Platform.Styles;component/RadioButtonResources.xaml\"/> <ResourceDictionary Source=\"/Sdl.Desktop.Platform.Styles;component/TreeViewResources.xaml\"/> <ResourceDictionary Source=\"/Sdl.Desktop.Platform.Styles;component/BindablePasswordBoxStyle.xaml\"/> <ResourceDictionary Source=\"/Sdl.Desktop.Platform.Controls;component/Controls/WatermarkTextBox/WatermarkTextBoxResources.xaml\"/> </ResourceDictionary.MergedDictionaries> </ResourceDictionary> Buttons There are several buttons styles exposed: Sdl.Button.PrimaryStyle Sdl.Button.SecondaryStyle Sdl.Button.HyperLinkStyle Sdl.Button.GeneralStyle Sdl.Button.WindowControlStyle After you import the resource you can use it as follows: <Button Style=\"{DynamicResource Sdl.Button.PrimaryStyle}\" Command=\"{Binding AddCommand}\" Content=\"Add TM\" HorizontalAlignment=\"Right\"/> Textboxes There are several textbox styles exposed, bellow you can see few examples: Sdl.TextBlock.TitleStyle Sdl.TextBlock.InformationTextEmphasisStyle Sdl.TextBlock.HyperLinkTextStyle Sdl.TextBlock.InformationTitleStyle Sdl.TextBlock.SubtitleStyle After you import the resource you can use it as follows: <TextBlock Style=\"{DynamicResource Sdl.TextBlock.TitleStyle}\" Text=\"Title style\" FontSize=\"14\"/> Data grid Bellow you can see an data grid code example <DataGrid Style=\"{DynamicResource Sdl.DataGrid.GenericStyle}\" Margin=\"10\" ItemsSource=\"{Binding PluginsCollection, Mode=TwoWay, UpdateSourceTrigger=PropertyChanged}\" SelectionUnit=\"FullRow\" GridLinesVisibility=\"None\"> <DataGrid.Columns> <DataGridTextColumn Width=\"*\" Header=\"Plugin name\" Binding=\"{Binding PluginName}\"/> <DataGridTextColumn Width=\"*\" Header=\"Studio versions\" Binding=\"{Binding StudioVersion}\"/> </DataGrid.Columns> </DataGrid> Groupbox and RadioButtons Code sample <GroupBox Style=\"{DynamicResource Sdl.GroupBox.SingleLineStyle}\" Header=\"Studio versions\" Width=\"300\" Margin=\"10\"> <StackPanel> <RadioButton Style=\"{DynamicResource Sdl.RadioButton.GenericStyle}\" GroupName=\"Studio\" Content=\"Studio 2019\" Margin=\"5\"/> <RadioButton Style=\"{DynamicResource Sdl.RadioButton.GenericStyle}\" GroupName=\"Studio\" Content=\"Studio 2021\" Margin=\"5\"/> </StackPanel> </GroupBox> Sdl.Desktop.Platform.Controls.dll In this API were released following Studio controls: Studio Control Description Numeric UpDown Represents a Windows box that displays numeric values. Up and Down buttons are available to increase/decrease the value from the box. TextBoxWatermark Custom textbox which display a custom set text as watermark and has a Clear button. Bindable PasswordBox Custom password box which allows you to obtain the Password in your viewmodel. Uniform WrapPanel Represents a wrapPanel which set the width of all childs to be the higher width between them SortWise DataGrid DataGrid with sorting capability In this API were released following Studio behaviours: | Studio Behaviour | Description | | ------------- | -----| | DragDrop | This behaviour easily allows you to get the dropped files or directories. First thing you need to do is to import the behaviours exposed by the API in your project, and attach it to a grid for example. You need to add your own implementation for DragDropCommand.| | WebBrowser Content Source | With this behaviour you can pass HTML code as source content to web browser.| | WebBrowser Bindable Source | This behaviour allows you to easily set the navigation URI in your view model. | TextBlock AutoToolTip | Using this behaviour you can add a tooltip to a textblock.| | WindowLoaded | With behaviour you can attach to your window loaded event.| | TreeView SelectedItem Changed | With behaviour you can attachto SelectedItem Changed event of a treeview.| How to use Studio Controls in your plugin? First of all you have to import the api in your application: <xmlns:controls=\"clr-namespace:Sdl.Desktop.Platform.Controls.Controls;assembly=Sdl.Desktop.Platform.Controls\"/> Watermark TextBox <xmlns:watermarkTextBox=\"clr-namespace:Sdl.Desktop.Platform.Controls.Controls.WatermarkTextBox;assembly=Sdl.Desktop.Platform.Controls\"/> <TextBox Style=\"{DynamicResource WatermarkTextBox}\" Text=\"{Binding SearchText, Mode=TwoWay, UpdateSourceTrigger=PropertyChanged}\" watermarkTextBox:TextBoxWatermarkHelper.WatermarkText =\"{Binding SearchWatermarkText}\" /> Above code is rendered as follows: After you start to type, Clear button will appear in the textbox, you need to give your own implementetion for clear command. An example of the command can be found bellow (CommandHandler implementation): private ICommand _clearCommand; public ICommand ClearCommand => _clearCommand ?? (_clearCommand = new CommandHandler(Clear, true)); private void Clear() { SearchText = string.Empty; SearchWatermarkText = \"Trados Studio 2021\"; } Bindable PasswordBox <controls:BindablePasswordBox Style=\"{DynamicResource Sdl.BindablePasswordBox.GenericStyle}\" Password=\"{Binding Password, Mode=TwoWay, UpdateSourceTrigger=PropertyChanged, ValidatesOnDataErrors=True}\" PasswordMaxLength=\"64\" /> In your view model you'll have Password property: private string _password; public string Password { get => _password; set { _password = value; OnPropertyChanged(nameof(Password)); } } Numeric UpDown <controls:NumericUpDown Style=\"{DynamicResource Sdl.NumericUpDown.Generic}\" Width=\"150\" HorizontalAlignment=\"Left\" Margin=\"10\"/> Drag&Drop Behaviour <xmlns:behaviours=\"clr-namespace:Sdl.Desktop.Platform.Controls.Behaviours;assembly=Sdl.Desktop.Platform.Controls\"/> <Grid Height=\"100\" Background=\"GhostWhite\" AllowDrop=\"True\" behaviours:DragDropBehaviour.DragDrop=\"{Binding DragDropCommand}\"/> In the example bellow we implemented DragDropCommand command in view model RelayCommand implementation: public ICommand DragDropCommand => _dragDropCommand ?? (_dragDropCommand = new RelayCommand(DragAndDrop)); private void DragAndDrop(object parameter) { if (parameter == null || !(parameter is DragEventArgs eventArgs)) return; var fileDrop = eventArgs.Data.GetData(DataFormats.FileDrop, false); if (fileDrop is string[] filesOrDirectories && filesOrDirectories.Length > 0) { foreach (var fullPath in filesOrDirectories) { var fileAttributes = File.GetAttributes(fullPath); if (fileAttributes.HasFlag(FileAttributes.Directory)) { //is directory } //is file } } } Window loaded Behaviour <behaviours:WindowLoadedBehaviour.Loaded =\"{Binding WindowLoadedCommand}\"/> WebBrowser BindableSource Behavior <WebBrowser behaviours:WebBrowserBindableSourceBehavior.BindableSource =\"{Binding Uri, UpdateSourceTrigger=PropertyChanged}\"/> TextBlock AutoToolTip Behavior <TextBox behaviours:TextBlockAutoToolTipBehavior.AutoTooltip=\"True\" ToolTip=\"This is a tooltip\" Text=\"Trados Studio 2021 /> WebBrowser Content Source <WebBrowser behaviours:WebBrowserContentSource.Html =\"{Binding Content, UpdateSourceTrigger=PropertyChanged}\"/> Content =\"<html>\\r\\n<body>\\r\\n\\r\\n<p>This is a paragraph.</p>\\r\\n<p>This is another paragraph.</p>\\r\\n\\r\\n</body>\\r\\n</html>\"; Above code is rendered as follows:"
   },
-  "articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2024.html": {
-    "href": "articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2024.html",
-    "title": "How to update plugins to Trados Studio 2024",
-    "summary": "How to update plugins to 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 2024. 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. 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: 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. Name should be set to: TradosStudio Example <?xml version=\"1.0\" encoding=\"utf-8\"?> <PluginPackage xmlns=\"http://www.sdl.com/Plugins/PluginPackage/1.0\"> <PlugInName>My plugin name</PlugInName> <Version>1.1.0.0</Version> <Description>My plugin description</Description> <Author>Trados AppStore Team</Author> <RequiredProduct name=\"TradosStudio\" minversion=\"18.0\" maxversion=\"18.9\" /> </PluginPackage> 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. Production BETA Installation path: $(MSBuildProgramFiles32)\\Trados\\Trados Studio\\Studio18: <Reference Include=\"Sdl.Desktop.IntegrationApi.Extensions\"> <HintPath>$(MSBuildProgramFiles32)\\Trados\\Trados Studio\\Studio18\\Sdl.Desktop.IntegrationApi.Extensions.dll</HintPath> </Reference> Plugin deployment path: $(AppData)\\Trados\\Trados Studio\\18\\Plugins: <PluginDeploymentPath>$(AppData)\\Trados\\Trados Studio\\18\\Plugins</PluginDeploymentPath> Installation path: $(MSBuildProgramFiles32)\\Trados\\Trados Studio\\Studio18Beta: <Reference Include=\"Sdl.Desktop.IntegrationApi.Extensions\"> <HintPath>$(MSBuildProgramFiles32)\\Trados\\Trados Studio\\Studio18Beta\\Sdl.Desktop.IntegrationApi.Extensions.dll</HintPath> </Reference> Plugin deployment path: $(AppData)\\Trados\\Trados Studio\\18Beta\\Plugins: <PluginDeploymentPath>$(AppData)\\Trados\\Trados Studio\\18Beta\\Plugins</PluginDeploymentPath> 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 The following are a list of known issues and solutions that you might encounter depending on your settings and configuration: 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: Trados.Community.Toolkit.Core Trados.Community.Toolkit.LanguagePlatform Trados.Community.Toolkit.Integration Trados.Community.Toolkit.FileType 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. <?xml version=\"1.0\" encoding=\"utf-8\" ?> <configuration> <startup> <supportedRuntime version=\"v4.0\" sku=\".NETFramework,Version=v4.8\" /> </startup> <runtime> <NetFx40_PInvokeStackResilience enabled=\"1\" /> <legacyCorruptedStateExceptionsPolicy enabled=\"true\" /> <ThrowUnobservedTaskException enabled=\"true\" /> <assemblyBinding xmlns=\"urn:schemas-microsoft-com:asm.v1\"> <dependentAssembly> <assemblyIdentity name=\"Microsoft.Extensions.DependencyModel\" publicKeyToken=\"adb9793829ddae60\" culture=\"neutral\" /> <bindingRedirect oldVersion=\"0.0.0.0-7.0.0.0\" newVersion=\"7.0.0.0\" /> </dependentAssembly> </assemblyBinding> </runtime> </configuration>"
-  },
-  "articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2024_sr1.html": {
-    "href": "articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2024_sr1.html",
-    "title": "How to update plugins to Trados Studio 2024 SR1",
-    "summary": "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 version=\"1.0\" encoding=\"utf-8\"?> <PluginPackage xmlns=\"http://www.sdl.com/Plugins/PluginPackage/1.0\"> <PlugInName>My plugin name</PlugInName> <Version>1.1.0.0</Version> <Description>My plugin description</Description> <Author>Trados AppStore Team</Author> <RequiredProduct name=\"TradosStudio\" minversion=\"18.1\" maxversion=\"18.1.9\" /> </PluginPackage> Ensure RequiredProduct reflects minversion=\"18.1\" and maxversion=\"18.1.9\". Project References & Deployment Path Update references and deployment settings in your .csproj: Production BETA References: Set Trados Studio assemblies to use the Studio 18 path: <Reference Include=\"Sdl.Desktop.IntegrationApi.Extensions\"> <HintPath>$(MSBuildProgramFiles32)\\Trados\\Trados Studio\\Studio18\\Sdl.Desktop.IntegrationApi.Extensions.dll</HintPath> </Reference> Deployment Path: <PluginDeploymentPath>$(AppData)\\Trados\\Trados Studio\\18\\Plugins</PluginDeploymentPath> References: Set Trados Studio assemblies to use the Studio 18 Beta path: <Reference Include=\"Sdl.Desktop.IntegrationApi.Extensions\"> <HintPath>$(MSBuildProgramFiles32)\\Trados\\Trados Studio\\Studio18Beta\\Sdl.Desktop.IntegrationApi.Extensions.dll</HintPath> </Reference> Deployment Path: <PluginDeploymentPath>$(AppData)\\Trados\\Trados Studio\\18Beta\\Plugins</PluginDeploymentPath> 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 version=\"1.0\" encoding=\"utf-8\" ?> <configuration> <configSections> <section name=\"BestMatchServiceUrlsConfig\" type=\"Sdl.BestMatchServiceStudioIntegration.Common.UrlsConfig, Sdl.BestMatchServiceStudioIntegration.Common\" /> </configSections> <BestMatchServiceUrlsConfig GlobalApi=\"https://api.cloud.trados.com\" auth0=\"https://sdl-prod.eu.auth0.com\"> <LanguageConfig> <Lang Code=\"en\" /> <Lang Code=\"de\" /> <Lang Code=\"fr\" /> <Lang Code=\"es\" /> <Lang Code=\"ja\" /> <Lang Code=\"it\" /> <Lang Code=\"zh-CN\" /> </LanguageConfig> <HavingTroubleSigningIn url=\"https://gateway.sdl.com/apex/communityknowledge?articleName=000001399\" /> </BestMatchServiceUrlsConfig> <runtime> <NetFx40_PInvokeStackResilience enabled=\"1\" /> <legacyCorruptedStateExceptionsPolicy enabled=\"true\" /> <ThrowUnobservedTaskException enabled=\"true\" /> <assemblyBinding xmlns=\"urn:schemas-microsoft-com:asm.v1\"> <dependentAssembly> <assemblyIdentity name=\"Microsoft.Extensions.DependencyModel\" publicKeyToken=\"adb9793829ddae60\" culture=\"neutral\" /> <bindingRedirect oldVersion=\"0.0.0.0-7.0.0.0\" newVersion=\"7.0.0.0\" /> </dependentAssembly> </assemblyBinding> </runtime> <startup> <supportedRuntime version=\"v4.0\" sku=\".NETFramework,Version=v4.8\" /> </startup> </configuration> 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: 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: 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 NuGet package for this sample: 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 // 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."
+  "articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2026.html": {
+    "href": "articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2026.html",
+    "title": "How to update plugins to Trados Studio 2026 Release",
+    "summary": "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. 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: <PropertyGroup> ... <PlatformTarget>x64</PlatformTarget> ... </PropertyGroup> 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. 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 version=\"1.0\" encoding=\"utf-8\"?> <PluginPackage xmlns=\"http://www.sdl.com/Plugins/PluginPackage/1.0\"> <PlugInName>My plugin name</PlugInName> <Version>1.0.0.0</Version> <Description>My plugin description</Description> <Author>Trados AppStore Team</Author> <RequiredProduct name=\"TradosStudio\" minversion=\"19.0\" maxversion=\"19.9\" /> </PluginPackage> Ensure RequiredProduct reflects minversion=\"19.0\" and maxversion=\"19.9\". Project References & Deployment Path Update references and deployment settings in your .csproj: Production BETA References: Set Trados Studio assemblies to use the Studio 19 path: <Reference Include=\"Sdl.Desktop.IntegrationApi.Extensions\"> <HintPath>$(ProgramFiles)\\Trados\\Trados Studio\\Studio19\\Sdl.Desktop.IntegrationApi.Extensions.dll</HintPath> </Reference> Deployment Path: <PluginDeploymentPath>$(AppData)\\Trados\\Trados Studio\\19\\Plugins</PluginDeploymentPath> References: Set Trados Studio assemblies to use the Studio 19 Beta path: <Reference Include=\"Sdl.Desktop.IntegrationApi.Extensions\"> <HintPath>$(ProgramFiles)\\Trados\\Trados Studio\\Studio19Beta\\Sdl.Desktop.IntegrationApi.Extensions.dll</HintPath> </Reference> Deployment Path: <PluginDeploymentPath>$(AppData)\\Trados\\Trados Studio\\19Beta\\Plugins</PluginDeploymentPath> 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. If the project is SDK-style, then unloading/reloading is unnecessary. 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 version=\"1.0\" encoding=\"utf-8\" ?> <configuration> <configSections> <section name=\"BestMatchServiceUrlsConfig\" type=\"Sdl.BestMatchServiceStudioIntegration.Common.UrlsConfig, Sdl.BestMatchServiceStudioIntegration.Common\" /> </configSections> <BestMatchServiceUrlsConfig GlobalApi=\"https://api.cloud.trados.com\" auth0=\"https://sdl-prod.eu.auth0.com\"> <LanguageConfig> <Lang Code=\"en\" /> <Lang Code=\"de\" /> <Lang Code=\"fr\" /> <Lang Code=\"es\" /> <Lang Code=\"ja\" /> <Lang Code=\"it\" /> <Lang Code=\"zh-CN\" /> </LanguageConfig> <HavingTroubleSigningIn url=\"https://gateway.sdl.com/apex/communityknowledge?articleName=000001399\" /> </BestMatchServiceUrlsConfig> <runtime> <NetFx40_PInvokeStackResilience enabled=\"1\" /> <legacyCorruptedStateExceptionsPolicy enabled=\"true\" /> <ThrowUnobservedTaskException enabled=\"true\" /> <assemblyBinding xmlns=\"urn:schemas-microsoft-com:asm.v1\"> <dependentAssembly> <assemblyIdentity name=\"Microsoft.Extensions.DependencyModel\" publicKeyToken=\"adb9793829ddae60\" culture=\"neutral\" /> <bindingRedirect oldVersion=\"0.0.0.0-7.0.0.0\" newVersion=\"7.0.0.0\" /> </dependentAssembly> </assemblyBinding> </runtime> <startup> <supportedRuntime version=\"v4.0\" sku=\".NETFramework,Version=v4.8\" /> </startup> </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 Working with BCMs The BCM-related classes have been moved from Sdl.LanguagePlatform.TranslationMemoryApito TradosStudio.BcmLite: <Reference Include=\"TradosStudio.BcmLite\"> <HintPath>$(ProgramFiles)\\Trados\\Trados Studio\\Studio19\\TradosStudio.BcmLite.dll</HintPath> </Reference> And some classes were renamed: LiteDocument to Document LiteFragment to DocumentFragment The LiteBcmVisitor abstract class now includes two more methods: 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: using Sdl.Terminology.TerminologyProvider.Core; // Example URI for your termbase string termbaseUriString = \"ttb.file:///C:/Termbases/MyTermbase.ttb\"; 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 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; // 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 Release. This includes the following assemblies: Trados.Community.Toolkit.Core Trados.Community.Toolkit.LanguagePlatform Trados.Community.Toolkit.Integration Trados.Community.Toolkit.FileType Trados.Community.Toolkit.ProjectAutomation"
   },
   "articles/hints_tips/UsefulTips/UsefulTipsApiArticle.html": {
     "href": "articles/hints_tips/UsefulTips/UsefulTipsApiArticle.html",
@@ -11012,7 +11007,7 @@
   "index.html": {
     "href": "index.html",
     "title": "Access the Var:ProductNameWithEdition APIs",
-    "summary": "Access the Var:ProductNameWithEdition APIs Getting started with Var:ProductNameWithEdition APIs Read more on how you can write your first Var:ProductName plugin. Learn more about Var:ProductNameWithEdition APIs Learn more about the APIs and what you can achieve with them. How to update plugins to Var:ProductNameWithEdition Learn more about how you can make your plugin compatible with Var:ProductNameWithEdition. Articles Read articles on how to get more out of Var:ProductName. Code samples Find more of our code samples on GitHub. Open Source Community Projects Join our community-driven repository of Var:ProductName plugins on RWS Community. Var:ProductName API versions Var:ProductName 2024 - API 18.0 Var:ProductName 2022 - API 17.2 Var:ProductName 2022 - API 17.1 Var:ProductName 2022 - API 17.0 Var:ProductName 2021 SR2 - API 16.2 Var:ProductName 2021 SR1 - API 16.1 Var:ProductName 2019 - API 15.2"
+    "summary": "Access the Var:ProductNameWithEdition APIs Getting started with Var:ProductNameWithEdition APIs Read more on how you can write your first Var:ProductName plugin. Learn more about Var:ProductNameWithEdition APIs Learn more about the APIs and what you can achieve with them. How to update plugins to Var:ProductNameWithEdition Learn more about how you can make your plugin compatible with Var:ProductNameWithEdition. Articles Read articles on how to get more out of Var:ProductName. Code samples Find more of our code samples on GitHub. Open Source Community Projects Join our community-driven repository of Var:ProductName plugins on RWS Community. Var:ProductName API versions Var:ProductName 2024 SR1 - API 18.1 Var:ProductName 2024 - API 18.0 Var:ProductName 2022 - API 17.2 Var:ProductName 2022 - API 17.1 Var:ProductName 2022 - API 17.0 Var:ProductName 2021 SR2 - API 16.2 Var:ProductName 2021 SR1 - API 16.1 Var:ProductName 2019 - API 15.2"
   },
   "writing_guidelines.html": {
     "href": "writing_guidelines.html",
diff --git a/manifest.json b/manifest.json
index 0841ce237..478dfb5f8 100644
--- a/manifest.json
+++ b/manifest.json
@@ -33147,20 +33147,10 @@
     },
     {
       "type": "Conceptual",
-      "source_relative_path": "articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2024.md",
+      "source_relative_path": "articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2026.md",
       "output": {
         ".html": {
-          "relative_path": "articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2024.html"
-        }
-      },
-      "version": ""
-    },
-    {
-      "type": "Conceptual",
-      "source_relative_path": "articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2024_sr1.md",
-      "output": {
-        ".html": {
-          "relative_path": "articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2024_sr1.html"
+          "relative_path": "articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2026.html"
         }
       },
       "version": ""