Hello again,

I investigated further and must correct some elements above. Former version was 17.0.6 (not SR1) but it was already a problem that I didn't notice.

After a proper update of the AssemblyResolver project from Github, the problem with missing "npgsql.dll" and "microsoft.data.sqlclient.dll" has been solved, but "sqlite.interop.dll" was still not recognized. Trying to add this dll as nuget directly is still impossible. (see above)

I also tried to use the AssemblyResolver nuget instead aof my compiled version, but there was the error that the assembly should have a strong name.

Thanks

Sébastien

Hello again,

I investigated further and must correct some elements above. Former version was 17.0.6 (not SR1) but it was already a problem that I didn't notice.

After a proper update of the AssemblyResolver project from Github, the problem with missing "npgsql.dll" and "microsoft.data.sqlclient.dll" has been solved, but "sqlite.interop.dll" was still not recognized. Trying to add this dll as nuget directly is still impossible. (see above)

I also tried to use the AssemblyResolver nuget instead aof my compiled version, but there was the error that the assembly should have a strong name.

Thanks

Sébastien

Hi Sébastien Desautel , is there a reason you can't use the latest release of the product SR2?

Have you tried making reference to the sqllite.interop from the Trados Studio installation and simply adding the binding redirect?
     <dependentAssembly>
       <assemblyIdentity name="Microsoft.Data.SqlClient" publicKeyToken="23ec7fc2d6eaa4a5" culture="neutral" />
       <bindingRedirect oldVersion="0.0.0.0-5.0.0.0" newVersion="5.0.0.0" />
     </dependentAssembly>

Hello Patrick, thanks for looking into this.

I will try with SR2 as soon as I can (not yet possible in my environment). Adding a reference to the sqlite.interop.dll from the Trados Studio installation folder also casts the following error: adding reference to "SQLite.Interop" Make sure that the file is accessible and that it is a valid assembly or COM component.

Adding the <dependentAssembly> as suggested did not help on it's own, but I think you suggested this along with the reference to the dll, right?

I have found 2 solutions:
- a previous post in the community suggested copying the dll directly to the compile destination folder (bin/debug) and this helped.
- I also tried importing a larger sqlite nuget (System.Data.Sqlite) and this also helped.

After importing the larger nuget, I also did a test without AssemblyResolver, and to my surprise it still works. Do you know maybe why?

Anyway, this seems to be fixed.

Thanks

Sébastien

FYI I've just realized that I had already the Microsoft.Data.SqlClient nuget install in my project. This may explain the above statements.

Hi Sébastien Desautel , seems to be a problem with resolving dependencies. I'd remove the nuget package from your project and simply reference the sqlite interop assembly from the Studio installation folder (especially if they are different versions) as you'll run in to these issues when attempting to load your app/plugin in the studio context

Thank you Patrick , I will do that.