From adc3d8a0bbb5806d3463df23f83312fbc614db69 Mon Sep 17 00:00:00 2001 From: Robert Cornea Date: Mon, 8 Jun 2026 10:58:52 +0300 Subject: [PATCH] - update how to upgrade section --- .../setting_up_a_developer_machine.md | 11 +- .../gettingstarted/studio_plugin_overview.md | 9 +- .../how_to_update_plugins_to_trados_studio.md | 140 ++++-------------- 3 files changed, 35 insertions(+), 125 deletions(-) diff --git a/articles/gettingstarted/setting_up_a_developer_machine.md b/articles/gettingstarted/setting_up_a_developer_machine.md index 8e860400cb..9bab193e4c 100644 --- a/articles/gettingstarted/setting_up_a_developer_machine.md +++ b/articles/gettingstarted/setting_up_a_developer_machine.md @@ -5,18 +5,17 @@ Make sure you have the right prerequisites and meet the system requirements to d ## Prerequisites * For the development environment, we recommend using Var:VisualStudioEdition. -* You need a licensed Var:ProductNameWithEdition or later installed on your development machine. + +* If you develop against a version of the API distributed with one of RWS's publicly released applications (i.e. Var:ProductNameWithEdition), all required assemblies and files should be available alongside the application. + Make sure you have the latest release of Var:ProductName installed. + * We also recommend installing the **Var:ProductName SDK** on your machine. After installing the **Var:ProductName SDK**, the **New Project** dialog box in Var:VisualStudioEdition displays additional project templates specific to Var:ProductName application development. - * You can get the latest version from the [developer hub](https://developers.rws.com/). + * You can get the latest version from the [public repository](https://github.com/RWS/trados-studio-vs-extension). * Or you can install directly from Var:VisualStudioEdition -> Tools -> Extensions. ![Visual Studio Extensions](images/VisualStudioExtensions.png) -* If your implementations need to connect to a TM Server system, make sure that the TM Server also runs the latest version. -* If you develop against a version of the API distributed with one of RWS's publicly released applications (i.e. Var:ProductNameWithEdition), all required assemblies and files should be available alongside the application. - Make sure you have the latest release of Var:ProductName installed. - > [!NOTE] > > As the build output path for your implementations, choose Var:PluginPackedPath. diff --git a/articles/gettingstarted/studio_plugin_overview.md b/articles/gettingstarted/studio_plugin_overview.md index e1b53ba38e..5cd3ecb7fb 100644 --- a/articles/gettingstarted/studio_plugin_overview.md +++ b/articles/gettingstarted/studio_plugin_overview.md @@ -9,12 +9,9 @@ For more information on building specific types of plug-ins, refer to the releva ## Var:ProductName Plug-in Support -The core Var:ProductName application uses a modular architecture consisting entirely of plug-ins. -These plug-ins are known as *system plug-ins*. -You cannot add system plug-ins to an existing Var:ProductName installation, and end-users cannot disable them. - -In addition to system plug-ins, Var:ProductName supports various types of *third-party plug-ins*. -Third-party developers can build these plug-ins using the **Var:ProductName SDK** and deploy them into an existing Var:ProductName installation. +Var:ProductName exposes various public APIs that allow you to extend the application by building plug-ins that integrate with the core application and provide additional features and functionalities. +Third-party developers can build these plug-ins using the **Var:ProductName SDK** and deploy them into an +existing Var:ProductName installation. This section focuses on third-party plug-in development and deployment. Since Var:ProductName is a Microsoft .NET application, develop third-party plug-ins using **Microsoft .NET Framework 4.8**. diff --git a/articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio.md b/articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio.md index 730b25a8ce..e3647e3a62 100644 --- a/articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio.md +++ b/articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio.md @@ -101,140 +101,54 @@ Standalone integrations may require binding redirects. Example for `App.config`: ```xml - -
- - - - - - - - - - - - - - - - - - - - - - - - - - + - - + + + + - - + + + + - - + + + + - - + + + + - - + + + + - - + + + + - - + + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ``` In most cases, this will be sufficient to enable proper interaction with the Studio APIs.