• State Verified Answer
  • Replies 4 replies
  • Subscribers 393 subscribers
  • Views 418 views
  • Users 0 members are here
Options
Related

Publishing plugin for Trados Studio 2022 and 2022 SR1

Rob Cole
Hi SDL Community,
I hope everyone is doing well.
We have a plugin for Trados Studio 2022 published at RWS App Store, which was compatible with very initial versions of Studio 2022. Then RWS released Studio 2022 SR1, which started throwing following error upon using that published plugin:
Error message in Trados Studio stating 'Method not found: 'System.Globalization.CultureInfo Sdl.LanguagePlatform.Core.LanguagePair.get_SourceCulture()'.
We build a new plugin by using Studio 2022 SR1 SDKs and off course by using objects of new Classes to get language codes and culture information. Which actually solved the problem but we didn't get it published so far. One question we have is, how can we publish two plugins for different minor versions of Studio 2022?
Another problem one of our clients is facing is: They set up Trados Studio 2022 at a new machine for one translator, and they installed the plugin from the App Store which actually wasn't compatible with that minor version of Studio 2022. Then we shared the updated plugin with her, and she uninstalled the plugin and installed that new plugin, but the new one isn't working on that particular machine, whereas it is working for other members of her team on the exact same version of Studio 2022. We checked the folders mentioned in this article as well, but couldn't find any trace of the old plugin. What could be the possible reason?
Thank you for always being so helpful.
Best regards,

Generated Image Alt-Text
[edited by: Trados AI at 1:42 PM (GMT 0) on 5 Mar 2024]
Rate translation
×
Suggest better translation
×
  • +1

     

    Rob Cole said:
    One question we have is, how can we publish two plugins for different minor versions of Studio 2022?

    All controlled by the plugin manifest.  The AppStore can support this. For SR1 only you'd use this:

    <RequiredProduct name="TradosStudio" minversion="17.1" maxversion="17.19" />

    For SR2 you'd use this:

    <RequiredProduct name="TradosStudio" minversion="17.2" maxversion="17.9" />

    This way the Trados Studio integration will not even see an unsupported version, and if the user downloads and double clicks the sdlplugin file any unsupported versions will be greyed out in the plugin manager.

    Rob Cole said:
    We checked the folders mentioned in this article as well, but couldn't find any trace of the old plugin. What could be the possible reason?

    Did you also check the unpacked?

    c:\Users\pfilkin\AppData\Roaming\Trados\Trados Studio\17\Plugins\Unpacked\

    If you don't remove that too then the plugin may not unpack and the old one will get used even though the plugin itself is different.

    Regards

    Paul.
  • 0 in reply to Paul

    Thank you Paul for the quick response. It is very helpful and makes it clear that we can publish plugins for separately for minor versions as well.

    Just to make it clear, that the plugin for very initial versions of Studio 2022 which contains function Sdl.LanguagePlatform.Core.LanguagePait.get_SourceCulture(), the manifest file should look like:

    <RequiredProduct name="TradosStudio" minversion="17.0" maxversion="17.09" />

    Regarding uninstalling old plugin, I guess they checked Unpacked folder as well but I will recheck with client. If we get updated plugin publish at App store, this problem will also go away or it can still impact? I am asking because if we get our updated plugins published this week, then we don't to ask client check folders etc.

    Thank you!
  • +1 in reply to Rob Cole

     

    Rob Cole said:

    the manifest file should look like:

    <RequiredProduct name="TradosStudio" minversion="17.0" maxversion="17.09" />

    Correct.

    Normally we would also start life with 17.0 and 17.9 with the optimism we won't need to update the plugins as there would not normally be breaking changes to the public API outside of a major release.  But recently there has been because of a lot of essential preparation work that has been takin place to improve the product as a whole.

    Rob Cole said:
    If we get updated plugin publish at App store, this problem will also go away or it can still impact?

    Generally the unpacked folder is replaced when you use the integrated appstore but this could still be a problem, especially if the other reason for the problem is that they didn't install into the roaming folders.  So good to check all these locations:

    %APPDATA%\Trados\Trados Studio\17\Plugins

    %LOCALAPPDATA%\Trados\Trados Studio\17\Plugins

    c:\ProgramData\Trados\Trados Studio\17\Plugins

    If it was me I'd simply advise users to delete the plugins from all these locations and start afresh.  You may avoid spending time trying to fix this.
  • 0 in reply to Paul

    Thank you Paul for all the details.

    Another update on uninstalling plugin that it got resolved by restarting machine after doing above mentioned steps. Now we will submit new plugins for publishing at App Store to let customers seamlessly download and install it from App Store.