Hi Rieko,

The assemblies are not registered in GAC so you need to reference them from the install location of Studio. I think that note is a bit misleading since if you use the Visual Studio templates or look at the samples you will actually see that the output is set to C:\Users\{User}\AppData\Roaming\SDL\SDL Trados Studio\11\Plugins\Packages .

Thank you Romulus for your answer!  As you say, if I use the provided template, the build get's created in C:\Users\{User}\AppData\Local\SDL\SDL Trados Studio\11\Plugins\Packages.  It looks like build process copies all the dll being used.  Will there be any problem if I just go ahead and copy all these dll next to my application?

Also, is there any chance SDL will work on registering them in GAC in the near future?

At the moment there no plans to have the SDK registered in GAC, but can you please let me know how this will help you ? To be honest I don't see a big difference of having them registered in GAC

Thank you so much for your quick answer!  

I am not using SDL templates, and I am not creating plugins.  I am creating a standalone application which will create a SDL project.  (somewhat similar to the sample application mentioned in producthelp.sdl.com/.../index.aspx )  The application is built using programming language called LabVIEW, which has some limitation with .net assembly as mentioned here: digital.ni.com/.../9E1CFF2B47EC4FD386257116005FAB3E

It would help us quite a bit if SDL SDK be registered in GAC.

Thank you so much for considering this!!!

Rieko

It may also be possible to add the Trados Studio installation folder to your PATH environment variable so that the appropriate DLLs can be found. There's a nice path editor available for free from patheditor2.codeplex.com

Hi Romulus,  I tried copying all the dlls right next to my executable.  Now, I am getting a bit different error message:

Error creating instance of FileBasedProject in assembly Sdl.ProjectAutomation.FileBased.FileBasedProject, Sdl.ProjectAutomation.FileBased, Version=3.0.0.0, Culture=neutral, PublicKeyToken=c28cdb26c445c888, (Sdl.ProjectAutomation.FileBased.LicensingException: License check failed, with exception: System.ArgumentException: Invalid filechck.dll

  at Sdl.Core.FileCheck.AbstractFileCheck..ctor(String fileCheckDll, Boolean validateCertificate)

  at Sdl.Core.FileCheck.NodeLockFileCheck..ctor(String fileCheckDll, Boolean validateCertificate)

Do you have any idea what the problem is?

Thank you!

Rieko

I'm afraid that copying the sdk files into your folder won't work. The crash you receive is because the SDK is not able to check the license. I think the only option you have is to have the application installed in the Studio folder. This is a bad thing I know but I think it's the only option.

I'm going to start a discussion internally to see what we can do to have the assemblies in GAC but this will take some time and it might not happen.

I am copying the complete folder of

C:\Program Files\SDL\SDL Trados Studio\Studio3

into the bin\debug folder and the bin\release folder of visual basic without problems.

You can copy the release folder to any location on e.g. the network and you can execute your application without problems.

On the other side I am facing a problem with the OneClick publishing facility of VB which is not working because of the missing assemblies which are no more registered in GAC ! With Trados 2007 this was working perfectly!

I have not found a solution to this so far. I have not used any Visual Studio templates so far but I guess this will not work either.

If someone has an idea I would be very grateful!

Rainer

Hi Romulus,

Any updates on how your internal discussion is going on regarding GAC?

Thank you!

Rieko

Hi Rainer,

I tried copying the complete folder, but I still received LicensingException error.  Was there any trick you played with to get rid of the LicensingException error?

Thank you!

Rieko

Hi Rieko,

no tricks applied as far as I can remember....we use a network license located on a dedicated server and it works!

When the application is using some Studio component the API is searching the licence before, either locally or network licence depending on the Studio settings of your client!

I guess it is searching for the connection in the registry to connect to the license server to check the version!

To use the API the Studio license must be the Studio Professional one!

Rainer

Hi Rieko,

no tricks applied as far as I can remember....we use a network license located on a dedicated server and it works!

When the application is using some Studio component the API is searching the licence before, either locally or network licence depending on the Studio settings of your client!

I guess it is searching for the connection in the registry to connect to the license server to check the version!

To use the API the Studio license must be the Studio Professional one!

Rainer