Hi Simon,

I think if you repair the version you want to use, it will take over the Studio file types (such as .sdlproj, .sdlxliff). So if you repair Studio 2019 after installing 2021, then 2019 will open on double-clicking SDLXLIFF files, for instance. I think this can be automated also but not sure how...

I hope this helps, thanks, Daniel

Hi Daniel

Thank you for the suggestion.

 I tested it on my machine already and it didn't behave as I hoped for. 

I have Studio 2019 and Studio 2022 on my machine. I did the Repair of Studio 2019 and checked with sdlproj which pointed to Studio 2022. - (I didn't check about .sdlxliff)

Then  I uninstalled Studio 2019 and reinstalled it again and after I restarted the computer, the results are the following:.

.sdlxliff -> pointing to Studio 2019 

.sdltm -> pointing to Studio 2019

.sdlproj - > pointing to Studio 2022

It's interesting that .sdltm and .sdlxliff file extensions are now associated with Trados Studio 2019 (this is partially  what I need :-) ), but .sdlproj remains associated with Trados Studio 2022.

The question I have now (and we will test this) is:  Will our custom developed application start Trados Studio 2019 or the "highest version Trados Studio" .

Will add more info later. 

Thank you.

OK - tagging David Watson  here also for potential comment - he knows the inner workings of the installation processes better than me... Thanks, Daniel

Hi 

Until we complete the internal testing, I wanted to update my initial mail with this extremely simplified explanation.

Our developer  Radivoj Fajt  explained to me, that he is using https://www.nuget.org/packages/Studio.AssemblyResolver to "pick up all the necessary info about  installed version of Trados Studio from which, the application is able to start Trados Studio and start using it. 

So the challenge for him is to be able to influence which Trados Studio version is started by the application.  The limitation is that older Trados Studio (2019) is to be started only for some users - due to compatibility issues.
For all other users our application should pick "the default" Trados Studio as resolved by Studio AssemblyResolver.

Regards, 

Simon

Hello, To fix the opening from Windows explorer you can check the Registry files from the KB: https://gateway.sdl.com/apex/communityknowledge?articleName=000002461

Usually when the repair does not fix the associations is that registry associations were changed outside of repairing Studio, for example when changing the program used to open the SDLPROJ from Windows. In such cases there are additional sdlproj_auto_file entries in the registry that should be removed or fixed to point to the correct Studio version.

Also, please be careful when using Studio.AssemblyResolver as the latest build/nuget doesn't support Studio 2022. It is not an official RWS component but we are hoping to get it updated. The code can be found here if someone would like to do it themselves :-)
 GitHub - cromica/Studio-AssemblyResolver: Assembly resolver for SDL Studio standalone applications

Hello, Simon Bratina !

The StudioAssemblyResolver has now been brought under our SDL Nuget profile and has been updated to include the latest version of Studio (2022).

Also, we added a new code sample explaining how to resolve assemblies to any version of Studio installed.

Please let us know if this helps in solving the issue.

Hello, Simon Bratina !

The StudioAssemblyResolver has now been brought under our SDL Nuget profile and has been updated to include the latest version of Studio (2022).

Also, we added a new code sample explaining how to resolve assemblies to any version of Studio installed.

Please let us know if this helps in solving the issue.

 Hello, Emanuel Albu !

Thank you for the info about update to StudioAssemblyResolver. I'll pass this info to our developer Radivoj Fajt  so that he can update us if it resolved the issue.