Hi Laurent,

Do you think you can create a sample Studio plugin on which you can reproduce this issue?

I can think of two things that can generate such a behavior and I would like to see which one of them is happening on your end.

Sorin

Dear Sorin,

Thank you for your prompt reply and also for your presentation of the APIs during the seminar last week. It was a very good demo.

I was also planning to try to develop a plugin in orde to move away from the application I have developed in order to have to install the application in the Studio3 Folder under Program FIles. However, for this, I have to work on a PC (Win7) where SP1 is installed and my local admin rights on this PC expired on 30 April. So I hope I can start creating a plugin on Monday as soon as I can reach someone who will extend my local admin rights. I have been working since yesterday on an XP machine with Studio 2014 installed. As you can see, a long and complicated story....

In the meantime, could you maybe share your thoughts with me and let me know about the two reasons you think that could generate that behaviour?

Thanks in advance for your support.

Regards,

Laurent

What is more likely is that you haven't set the useLegacyV2RuntimeActivationPolicy to true in your application app.config.

You can find more information about how to set it here: msdn.microsoft.com/.../ff770241(v=vs.100).aspx

Sorin

Dear Sorin,

This was indeed the reason of the problem. I have added the above-mentioned attribute to the startup tag of my app.config and it solved the problem.

Thank you very much for your support.

Regards,

Laurent

PS: if create a plug-in to replace the application, should I add the attribute in the app.config or is it already provided via the plug-in template?

If you create a Studio plugin you don't have to specify that flag, because is already specified in SDLTradosStudio.exe.config.

Thanks for the information and for your support.

Much appreciated!