Hi Delfina,

Here is an answer from an SDL development architect;

If the Packages folder is created, and contains an sdlplugin file, the cause

is most likely a reference to a non-validated Sdl dll. If, for example, you try

to do some term lookup in the modified bil sample, and add a reference to

Sdl.MultiTerm.TMO.Interop (and actually use it), the plugin won't load, and

won't tell you why. The lack of a notification for the developer is unfortunate

in that case... The list of valid public API dlls can be found here:

C:\Program Files (x86)\SDL\SDL Trados Studio\Studio2\pluginconfig.xml

Also keep in mind that you have to delete the "Unpacked" folder every

time you rebuild a plugin; Trados Studio will _not_ unpack the new version

if there already is an unpacked one.

Regards, Ian

Ian Davies  |  Senior Product Manager | SDL | Language Technologies Division |  +44 7826843819

Hi Delfina,

Here is an answer from an SDL development architect;

If the Packages folder is created, and contains an sdlplugin file, the cause

is most likely a reference to a non-validated Sdl dll. If, for example, you try

to do some term lookup in the modified bil sample, and add a reference to

Sdl.MultiTerm.TMO.Interop (and actually use it), the plugin won't load, and

won't tell you why. The lack of a notification for the developer is unfortunate

in that case... The list of valid public API dlls can be found here:

C:\Program Files (x86)\SDL\SDL Trados Studio\Studio2\pluginconfig.xml

Also keep in mind that you have to delete the "Unpacked" folder every

time you rebuild a plugin; Trados Studio will _not_ unpack the new version

if there already is an unpacked one.

Regards, Ian

Ian Davies  |  Senior Product Manager | SDL | Language Technologies Division |  +44 7826843819

Hi Ian,

I was able to narrow down the issue with rebuilding and invalud dll.

The problem is actually related to this question:

community.sdl.com/.../780.aspx

In the workaround you suggest there, I added the Sdl.FileTypeSupport.Framework.Implementation in my solution and in the class I just  included

using Sdl.FileTypeSupport.Framework.Integration;

because as noticed the Sdl.FileTypeSupport.Framework.Integration is not present as a dll to be included.

The line that is causing the issue is the suggested solution:

importer.FileTypeManager = new PocoFilterManager(true)

At the point when I it ,the new unpacked file gets created at the right location but it is not detected by the plugin and the plugin is no longer added.

Please advise.