RWS Community
RWS Community
  • Site

Trados Go

Trados Studio

Trados Ignite

Trados Team

Trados Accelerate

Trados Enterprise

Trados GroupShare

Passolo

MultiTerm

RWS AppStore

Connectors

Beta Groups

Managed Translation

MultiTrans

TMS

Trados Enterprise

WorldServer

Language Weaver

Language Weaver Edge

Language Weaver Connectors

Language Weaver in Trados Studio

 

 

Content Champions

Tridion Docs

Tridion Sites

Contenta

LiveContent

XPP

Trados Go Ideas

Trados Studio Ideas

Trados Ignite Ideas

Trados GroupShare Ideas

Trados Team Ideas

Trados Team Terminology Ideas

Trados Enterprise & Accelerate Ideas

MultiTerm Ideas

Passolo Ideas

RWS Appstore Ideas

Tridion Docs Ideas

Tridion Sites Ideas

Language Weaver Ideas

Language Weaver Edge Ideas

Managed Translation - Enterprise Ideas

TMS Ideas

WorldServer Ideas

Trados Enterprise Ideas

XPP Ideas

GroupShare Developers

Language Cloud Developers

MultiTerm Developers

Passolo Developers

Trados Studio Developers

Managed Translation Developers

TMS Developers

WorldServer Developers

Tridion Docs Developers

XPP Developers

Language Combinations by Language Services

RWS Training & Certification

Style Guides

Content Management Partners

LDE Korean Vendor Support

RWS Campus

Trados Approved Trainers

Nordic Tridion Docs User Group

Tridion West Coast User Group

Community Ops

RWS Community Internal Group

AURORA

Internal Trados Ideas

Linguistic Validation

Mercury

QA Tools

RI Operational Excellence

Trados Inspired

XPP Cloud

Recognition & Reward System

RWS Community Platform Related Questions

Community Solutions Hub (Trados)

About RWS

Events

RWS Services: Train AI & others

RWS Training & Certification

To RWS Support

  • Search
  • Translate

    Detecting language please wait for.......


    Powered by
  • User
  • Site
  • Search
  • User
  • Developers
  • Trados Portfolio
  • Trados Studio Developers
  • More
  • Cancel
Trados Studio Developers

Trados Studio Developers > Studio Developers WIKI

Update required to older versions of Studio plugins
  • Home
  • Trados Studio developers forum
  • Studio Developers WIKI
  • Studio Developers Blog
  • More
  • Cancel
  • New
Show Translation Options

Detecting language please wait for.......


Powered by
Trados Studio Developers requires membership for participation - click to join
  • -Trados Studio API
    • Developer Licences
    • +Getting Started
    • -Knowledgebase
      • +How to...
      • +Studio 2015
      • -Studio 2019
        • How to push notifications in Studio 2019
        • How to update plugins to Studio 2019
        • Update required to older versions of Studio plugins
      • +Studio 2021
      • +Trados Studio 2022

Update required to older versions of Studio plugins

A new version of Studio will be released soon which will have breaking changes, that means older versions of plugins are not compatible with Studio 2019. In older versions of the plugins manifest file needs to be updated with maxvalue attribute. Adding that attribute will prevent user to install an older version to Studio 2019.

Without maxversion attribute:

With maxversion attribute:

What should be updated

There are few steps you need to do make your plugin to support maxversion attribute:

  • From NuGet download the latest version of Sdl.Core.PluginFramework.Build (15.0.2)

  • Update pluginpackage.manifest.xml file by adding maxversion="15.0"  

  • Last step is to update csproj of the project. Right click on project-> Unload -> Edit .csproj

      

Search for <PluginDeploymentPath> and change 15 with (14 if you are updating a 2017 plugin or 12 if you are updating a 2015 plugin)

Original: <PluginDeploymentPath>$(AppData)\SDL\SDL Trados Studio\15\Plugins</PluginDeploymentPath>

Updated : <PluginDeploymentPath>$(AppData)\SDL\SDL Trados Studio\14\Plugins</PluginDeploymentPath>

Right click -> Reload solution -> Rebuild solution. 

To test if plugin is updated correctly :

  • Go to output path double click on plugin
  • Agree with terms and conditions ->Next
  • In the Grid with Studio Versions installed Studio 2019 should be disabled

 

Update:

If after rebuilding the solution you receive an error regarding "PluginDeploymentPath":

Please unload the solution -> open .csproj and make sure you don't have any references to Sdl.Core.PluginFramework.build besides the one you just downloaded from Nuget which points to 15.0.2 version:

Tags:

Update required
Studio 2017 plugins
New PluginFramework version
  • Share
  • History
  • More
  • Cancel
Related
Recommended
  • Our Terms of Use
  • Copyright
  • Privacy
  • Security
  • Anti-slavery Statement
  • Cookie Notice
  • YouTube