Hi Samuel Baldus , I'll review what you have reported this morning and circle back to you; thx reporting (y)

Hi Samuel Baldus , I've been able to reproduce and identify a possible issue with resolving Microsoft.Data.SqlClient, Version=4.1.0.0 with the latest release of Trados Studio SR1 outside of the Studio context (e.g. standalone apps).

I'll udpate the documentation with some tips on how to deal with these later on.  In the meantime can you please test on your end if adding these binding ridirects to your configuration file resolves the issue?

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <startup useLegacyV2RuntimeActivationPolicy="true">
    <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.8" />
  </startup>
  <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="System.Memory" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-4.0.1.1" newVersion="4.0.1.1" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="icu.net" publicKeyToken="416fdd914afa6b66" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-2.7.0.0" newVersion="2.7.0.0" />
      </dependentAssembly>
      <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>
    </assemblyBinding>
  </runtime>
</configuration>

Hi Patrick Andrew Hartnett ,

Thanks for looking into this for me.

Changing the app.config file forces the pre-translation to work...somewhat.

The Reports are now created:

But during processing, the console spits out errors.

Pre-translation:

Analysis:

And the error still displays in the .sdlproj file:

Hi Samuel Baldus , sorry to see this is still proceduing errors; can you confirm that you added a reference to Sdl.Core.Globalization.Async.dll to your project?

<Reference Include="Sdl.Core.Globalization.Async">
    <HintPath>$(MSBuildProgramFiles32)\Trados\Trados Studio\Studio17\Sdl.Core.Globalization.Async.dll</HintPath>
</Reference>

reference to relevant documentation: community.rws.com/.../how-to-update-plugins-to-trados-studio-2022-sr1

Hi Patrick Andrew Hartnett 

Yes, that DLL is already referenced.

Hi Samuel Baldus , can you share yr project with me?  there is def. a compatibility issue as it indicates a problem unable to initialize a class with a different signature.

Hi Patrick Andrew Hartnett ,

Sure, can you share your email address?

Kind regards

Samuel

Hi Samuel Baldus , was OoO last week.  My e-mail phartnett@rws.com

Hi Patrick Andrew Hartnett , 

Thanks, you've got mail.

Samuel

Hi Samuel Baldus ,  thx for sharing your code and being available for a sync/meeting yesterday to align/demonstrate these issues.

Here are my latest findings after reviewing this issue.

1. Processing automation tasks are successful after adding the binding redirects to the app.config; you also confirmed this.
2. The reason you are seeing the additional Info messages in the console output is because you have choosen to receive and write to std output (console) the processing messages from your app.config. If don't need these, then simply remove the implementation of Log4Net from your project.
3. I confirm that the Info messages that are written to std output do not interfere with the automation tasks themselves + they are not written to the project file.  I suspect that the messages that you are seeing in the project file are from an automation execution prior to updating the app.Config file with the binding redirects?
   Note: If you look/check from you screenshots above, the error messages that are written in the project file are different to info processing messages that are written to console output.

Can you please check/confirm again with a new project.  If the issue persists, we can schedule another sync/meeting.

Hi Samuel Baldus ,  thx for sharing your code and being available for a sync/meeting yesterday to align/demonstrate these issues.

Here are my latest findings after reviewing this issue.

1. Processing automation tasks are successful after adding the binding redirects to the app.config; you also confirmed this.
2. The reason you are seeing the additional Info messages in the console output is because you have choosen to receive and write to std output (console) the processing messages from your app.config. If don't need these, then simply remove the implementation of Log4Net from your project.
3. I confirm that the Info messages that are written to std output do not interfere with the automation tasks themselves + they are not written to the project file.  I suspect that the messages that you are seeing in the project file are from an automation execution prior to updating the app.Config file with the binding redirects?
   Note: If you look/check from you screenshots above, the error messages that are written in the project file are different to info processing messages that are written to console output.

Can you please check/confirm again with a new project.  If the issue persists, we can schedule another sync/meeting.

Hi Patrick Andrew Hartnett 

Thanks for the meeting, and the replies.

1. Agreed, and confirmed.
2. Updating the app.config with the removal of the log4net implementation does remove the errors in the console.
3. After (2), nothing is written to the .sdlproj file.

Prior to the change, albeit they were not the same as the ones displayed in the console, errors were written to the .sdlproj file.

I don't really understand the cause, but the solutions you've offered have allowed our projects to progress, which we really appreciate.

Thanks again, and hope to catch up with you in the near future.