While building a Trados plugin I've hit this problem...
Has this assembly been overlooked in the white-list of permitted references? Why would I be allowed to call it in a stand-alone .exe but I can't call it from inside Trados?
Kacper Peka said:As far as I know Studio checks if plugins are using non public assemblies and throws this error. Standalone application won't check if assembly is public or not that's why it works.
Another huge plus for standalone applications (and minus for illogical push for making everything a plugin, no matter if it makes any sense... like the SDLXLIFF Toolkit).
Can you offer any explanation as to why it's not a public assembly? I'm confused as to why it would be available to us in stand-alone SDK-referencing programs but not available to us for plug-ins. The (out-dated) documentation for the SDK has a walk-through of how to automate project processes and instructs us to use this assembly, but doesn't mention that it can only be used for executables and not plug-ins.
Hi Andrew. Sorry for late response.
You can check this blog post to get more details about it. Hope it helps.