Studio 2015 beta 1 was recently released and you can find more information about this release by going here (if you are not registered already please contact Paul). As an OpenExchange developer the next question which probably pops is if my Studio 2014 plugin will work on the new Studio version. The short answer is no and this is because Studio 2015 is build on a newer .NET version and there is a new plugin location from where Studio 2015 loads your plugins. There 3 main things that must be done in order to have your plugin ready for Studio 2015: Besides the new .NET Framework you also need to reference the new Studio API assemblies which have the same name as before is just that they are located in the Studio 2015 install folder.
As I mentioned in my introduction Studio 2015 is build against a newer version of Microsoft .NET, to be more precise is .Net Framework 4.5.2. This means that Studio 2014 plugins will not work since they are build against .Net Framework 4 and this is because you can have backward compatibility but there is no way to have future compatibility. So here are the exact steps you to recompile your plugin:
32-bit and 64-bit
Includes the .NET Framework 4.5.1
Includes the .NET Framework 4.5
Windows 7 SP1
Windows Vista SP2
Windows Server 2012 R2
Windows Server 2012 (64-bit edition)
Windows Server 2008 R2 SP1
The .NET Framework is supported in the Server Core Role with SP1 or later, but isn't supported on Windows Server 2008 R2 for Itanium-Based Systems.
Windows Server 2008 SP2
The .NET Framework is not supported in the Server Core Role.
Check this video to see the exact steps you need to do in Visual Studio to upgrade your plugin:
At this point your plugin should build against Studio 2015 assemblies.
The location from where Studio 2015 has been changed and this is because we wanted to be able to run Studio 2014 and Studio 2015 in parallel. There are 2 locations where you can deploy your plugin
SDL Plugin installer
With Studio 2015 we added and an installer for sdlplugin file types. This means when you double click an .sdlplugin file there will be an app that will guide you thru the installation steps. To see this in action just watch this video:
If you are not using Studio 2015 you can still benefit from this feature buy going to OpenExchange and install it from there.
Studio 2015 SDK will be released pretty soon but until then if you need to start a new plugin from scratch please use this Studio 2015 empty projects:
>about this release by going here
When I click the link I get "Access Denied: You do not have permission to view/download this item. ".
You need to be a member of the Studio Beta Group - community.sdl.com/.../studio_beta_group . To get access to this community please contact Paul
After using the offline installer as linked in this post, I still was not seeing the .NET Framework 4.5.2 option in the Target framework dropdown in the Project > Properties > Application section. After a search, this answer on Stack Overflow (stackoverflow.com/.../how-to-select-net-4-5-2-as-a-target-framework-in-visual-studio) directed me to download the .NET 4.5.2 Developer Pack. After doing that, I saw the option.
Thanks David. I will update the link to the one from the article which is the developer pack.
I'm getting ready to update my OpenExchange plugin for Studio 2015, and also working on doing the same for a project for a client. But I have a question. If I build against .NET 4.5.2 and the Studio 2015 libraries, will that plugin be backwards-compatible with Studio 2011 and Studio 2014?
For now I'm trying to do everything in one Visual Studio project, for simplicity when updating the code, etc. I have automated changing the framework and libraries, as well as the manifest, by creating custom build configurations. It works fine to create the three different plugin versions, but I was curious as to whether this was necessary, or whether I could just build one version against the new libraries and framework and have it be backwards-compatible for the older versions of Trados Studio.
As an experiment, I tried a test build targeting the 2015 libraries and v4.5.2 framework. It seemed to load ok in 2014, but threw an error in 2011. Does this mean it is necessary to generate separate plugin builds for each respective version of Studio? I would like to target 2011, 2014, and 2015.
If the user only has Studio 2014 installed on his machine it's highly probable that it won't have .Net 4.5.2 and in this case the Studio 2015 plugin will not work or you might get some weird behavior. To avoid that kind of situation I recommend to have separate builds.
Thanks Romulus. I hadn't thought about that. Good point.