Update required to older versions of Studio plugins

Paul Filkin — Thu, 07 May 2020 17:09:55 GMT

Current Revision posted to Studio Developers WIKI by Paul Filkin on 5/7/2020 5:09:55 PM

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

Update required to older versions of Studio plugins

Andrea-Melinda Ghisa — Wed, 25 Jul 2018 15:09:28 GMT

Revision 10 posted to Studio Developers WIKI by Andrea-Melinda Ghisa on 7/25/2018 3:09:28 PM

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

Update required to older versions of Studio plugins

Florentina Caputa — Fri, 20 Jul 2018 08:10:42 GMT

Revision 9 posted to Studio Developers WIKI by Florentina Caputa on 7/20/2018 8:10:42 AM

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

Update required to older versions of Studio plugins

Andrea-Melinda Ghisa — Fri, 20 Jul 2018 07:21:18 GMT

Revision 8 posted to Studio Developers WIKI by Andrea-Melinda Ghisa on 7/20/2018 7:21:18 AM

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

Update required to older versions of Studio plugins

Andrea-Melinda Ghisa — Fri, 13 Jul 2018 06:30:32 GMT

Revision 7 posted to Studio Developers WIKI by Andrea-Melinda Ghisa on 7/13/2018 6:30:32 AM

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

Tags: Update required, Studio 2017 plugins, New PluginFramework version

Update required to older versions of Studio plugins

Andrea-Melinda Ghisa — Fri, 13 Jul 2018 06:18:32 GMT

Revision 6 posted to Studio Developers WIKI by Andrea-Melinda Ghisa on 7/13/2018 6:18:32 AM

Without maxversion attribute:

With maxversion attribute:

What should be updated

Where 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

Tags: Update required, Studio 2017 plugins, New PluginFramework version

Update required to older versions of Studio plugins

Andrea-Melinda Ghisa — Fri, 13 Jul 2018 06:18:04 GMT

Revision 5 posted to Studio Developers WIKI by Andrea-Melinda Ghisa on 7/13/2018 6:18:04 AM

Without maxversion attribute:

With maxversion attribute:

What should be updated

Where 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

Tags: Update required, Studio 2017 plugins, New PluginFramework version

Update required to older versions of Studio plugins

Andrea-Melinda Ghisa — Fri, 13 Jul 2018 06:16:29 GMT

Revision 4 posted to Studio Developers WIKI by Andrea-Melinda Ghisa on 7/13/2018 6:16:29 AM

Without maxversion attribute:

With maxversion attribute:

What should be updated

Where 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 from the path:

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

Tags: Update required, Studio 2017 plugins, New PluginFramework version

Update required to Studio 2017 plugins

Andrea-Melinda Ghisa — Fri, 13 Jul 2018 06:15:51 GMT

Revision 3 posted to Studio Developers WIKI by Andrea-Melinda Ghisa on 7/13/2018 6:15:51 AM

Without maxversion attribute:

With maxversion attribute:

What should be updated

Where 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 from the path:

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

Tags: Update required, Studio 2017 plugins, New PluginFramework version

Update required to Studio 2017 plugins

Andrea-Melinda Ghisa — Fri, 13 Jul 2018 06:13:00 GMT

Revision 2 posted to Studio Developers WIKI by Andrea-Melinda Ghisa on 7/13/2018 6:13:00 AM

Without maxversion attribute:

With maxversion attribute:

What should be updated

Where 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 from the path:

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.

Tags: Update required, Studio 2017 plugins, New PluginFramework version

Update required to Studio 2017 plugins

Andrea-Melinda Ghisa — Fri, 13 Jul 2018 06:01:49 GMT

Revision 1 posted to Studio Developers WIKI by Andrea-Melinda Ghisa on 7/13/2018 6:01:49 AM

Without maxversion attribute:

With maxversion attribute:

Tags: Update required, Studio 2017 plugins, New PluginFramework version