• Replies 7 replies
  • Subscribers 350 subscribers
  • Views 5770 views
  • Users 0 members are here
Options
Related

Cannot load the plug-in for 2014 error.

Delfina Jovanovska

Hi,

I am trying to move an existing plugin to work with 2014. I tried changing just the properties or starting a new project and using the same code, but I keep getting this error:

“Cannot load the plug-in defined in “Trados2014Plugin.plugin.xml”. The plug-in contains references to SDL assemblies that have not been validated for use with third-party plugins."

The SDL assembly name is Sdl.FileTypeSupport.Framework.Core.Settings and the validation error is “SDL assembly reference is not public"

Thanks,Delfina
Rate translation
×
Suggest better translation
×
Parents Reply Children
  • in reply to Daniel Brockmann

    The CU3 helped with this issue and only for  Sdl.FileTypeSupport.Framework.Core.Settings , but now I am getting the same error for  Sdl.FileTypeSupport.Framework.Integration.

    Here is part of the code that I am trying to use and it’s failing because of the missing assembly.

    using Sdl.FileTypeSupport.Framework.Integration;

    namespace Sdl.Sdk.FileTypeSupport.Samples.Bil

    {

       class TmImporter

       {

           public void importXLIFFFile(string tmPath, string importFilePath)

           {

               FileBasedTranslationMemory tm = new FileBasedTranslationMemory(tmPath);

               TranslationMemoryImporter importer = new TranslationMemoryImporter(tm.LanguageDirection);

               importer.ChunkSize = 20;

               GetImpotSettings(importer.ImportSettings);

               importer.BatchImported += new EventHandler<BatchImportedEventArgs>(importer_BatchImported);

               importer.FileTypeManager = new PocoFilterManager(true);

               importer.Import(importFilePath);

           }

      }

    }

    Please note that this is related to :community.sdl.com/.../3760.aspx
  • in reply to Delfina Jovanovska

    Hi,

    the sample you are referring to was never meant to be used as a plug-in. that is the reason why the integration assembly is not in the whitelist.

    To sort this out, please use this line to get the file type manager:

    importer.FileTypeManager mgr = DefaultFileTypeManager.CreateInstance(true);

    That should give you the necessary functionality without actually referencing the Sdl.FileTypeSupport.Framework.Integration

    Regards

    Patrik
  • in reply to Patrik Mazanek

    Thanks Patrik,

    I gave that a try and I am getting errors on the “DefaultFileTypeManager” does not exist in the current context. What reference should I add for this?  Also I think it’s related but this line also fails on the error:

    “The type of namespace name “importer” could not be found” so  I am missing a using directive or an assembly reference

    Please advice.

    Delfina
  • in reply to Delfina Jovanovska

    I just found the missing assembly is : Sdl.FileTypeSupport.Framework.Core.Utilities.IntegrationApi