Unable find assembly error occurs when build Trados plugin on 2015 SP3 environment

Trados2015SP3 was released so I built my plugin on Trados 2015 SP3 environment. But plugin doesn't work if plugin was built on SP3 environment.(Please note that I didn't have any problems on SP2)

 

My plugin consists of .sdlplugin and class library(.dll) under Trados install folder.

But plugin could not load class library(.dll) correctly.

 

Here is fusionlog.

.

LOG: Using host configuration file:

LOG: Using machine configuration file from C:\Windows\Microsoft.NET\Framework\v4.0.30319\config\machine.config.

LOG: Post-policy reference: Test.ClassLibraryTest, Version=1.0.6275.26138, Culture=neutral, PublicKeyToken=69f752e6db3550ab

LOG: GAC Lookup was unsuccessful.

LOG: Attempting download of new URL file:///C:/Program Files (x86)/SDL/SDL Trados Studio/Studio4/Test.ClassLibraryTest.DLL.

LOG: Assembly download was successful. Attempting setup of file: C:\Program Files (x86)\SDL\SDL Trados Studio\Studio4\Test.ClassLibraryTest.dll

LOG: Entering run-from-source setup phase.

LOG: Assembly Name is: Test.ClassLibraryTest, Version=1.0.6275.26237, Culture=neutral, PublicKeyToken=69f752e6db3550ab

WRN: Comparing the assembly name resulted in the mismatch: Revision Number

ERR: The assembly reference did not match the assembly definition found.

 

 

Here is assembly version.

PS C:\Program Files (x86)\SDL\SDL Trados Studio\Studio4> [System.Reflection.Assembly]::LoadFrom("C:\Program Files (x86)\

SDL\SDL Trados Studio\Studio4\Test.ClassLibraryTest.dll").GetName().Version

 

Major Minor Build Revision

----- ----- ----- --------

1     0     6275   26237

 

 

If plugin was built on SP3 environment, why does Trados try to load incorrect version assemblies?

 

 

Please note that when i replaced files under C:\Program Files (x86)\MSBuild\SDL\SDLTradosStudio\12 with SP2 and built again, plugin worked fine.

 

Does anyone meet same problem?

Is there any solutions for this problem ?

 

Best regards,

Masayuki

Parents
  • Why do you deploy the client library inside the Trados Studio folder? The .sdlplugin file should be deployed under one of the 3 locations from where Studio will load it (this is handled by the plugin installer when you click the .sdplugin file). During development the file will be copied automatically under user AppData\Roaming folder.

    Also your library should be included in the plugin package rather than copied inside Studio folder. You can do that from the plugin manifest file. More on that here

    Can you please give me more details on why you deploy the library inside Trados Studio folder as this is not normal when you build a plugin?

    Romulus Crisan | Translation Productivity Development Manager | SDL | (twitter) @cromica_82 | (blog) http://www.romuluscrisan.com/

Reply
  • Why do you deploy the client library inside the Trados Studio folder? The .sdlplugin file should be deployed under one of the 3 locations from where Studio will load it (this is handled by the plugin installer when you click the .sdplugin file). During development the file will be copied automatically under user AppData\Roaming folder.

    Also your library should be included in the plugin package rather than copied inside Studio folder. You can do that from the plugin manifest file. More on that here

    Can you please give me more details on why you deploy the library inside Trados Studio folder as this is not normal when you build a plugin?

    Romulus Crisan | Translation Productivity Development Manager | SDL | (twitter) @cromica_82 | (blog) http://www.romuluscrisan.com/

Children