I keep having issues with the dependent assemblies of Azure.AI.FormRecognizer.4.1.0 in visual studio c# project

Diallo, Mouhamadou S 0

WARNING! There was an error parsing the document

Hello,  
I'm trying to test the Azure.AI.FormRecognizer.4.1.0 in visual studio .net framework 4.8.1 library project solution. Now I've the version 6.0.0.1 of System.Diagnostics.DiagnosticSource in my solution, but when I try to downgrade the assembly assembly 'System.Diagnostics.DiagnosticSource' to the version 6.0.0.0, it will do the following downgrade as well (e.g: Azure.AI.FormRecognizer.4.1.0 to Azure.AI.FormRecognizer.4.0.0). Now if I downgrade to Azure.AI.FormRecognizer.4.0.0, I get the following error message: Could not load file or assembly  System.Diagnostics.DiagnosticSource, Version=4.0.4.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'. And after I install System.Diagnostics.DiagnosticSource, Version=4.0.4.0, I get another error message (Could not load file or assembly 'System.Runtime.CompilerServices.Unsafe, Version=4.0.4.1, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'). So I keep getting error after upgrading or downgrading assemblies version. How could I resolve this?  
  
Updates:
Azure.AI.FormRecognizer.4.1.0 -> Azure.AI.FormRecognizer.4.0.0
Azure.Core.1.34.0 -> Azure.Core.1.33.0
System.Diagnostics.DiagnosticSource.6.0.1 -> System.Diagnostics.DiagnosticSource.6.0.0


  
  
Exception thrown: 'System.IO.FileNotFoundException' in Azure.AI.FormRecognizer.dll
An exception of type 'System.IO.FileNotFoundException' occurred in Azure.AI.FormRecognizer.dll but was not handled in user code
Could not load file or assembly 'System.Diagnostics.DiagnosticSource, Version=6.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies. The system cannot find the file specified.  
  
![User's image](/api/attachments/cb22b3e9-6ae0-4fc2-a131-909b8e0db635?platform=QnA)  
  


Thanks & Regards,  
Mouhamadou

1 answer

Michael Taylor 51,341 Reputation points

2024-01-30T17:37:07.89+00:00
Azure.AI.FormRecognizer 4.1.0 requires at least Azure.Core 1.34.0. Azure Core requires at least System.Diagnostics.DiagnosticSource 6.0.1 for .NET Framework 4.7.2 or higher. Since you are targeting 4.8.1 you cannot downgrade DiagnosticSource to 6.0.0. Why are you trying to downgrade?

Downgrading packages can get tricky because of binding redirects. If you want to downgrade to Azure.AI.FormRecognizer 4.0.0 then downgrade the package using NuGet Package Manager. After that you'll need to fix up the binding redirects. I assume that you have an app/web.config file for your executable. Inside there is a binding redirect element that lists all the assemblies that you rely on and their version. You need to adjust the binding for any package you downgrade to use the version of the assembly that you are now targeting. As example if you updated to 4.1.0 then you most likely had something like this.

<dependentAssembly> <assemblyIdentity name="Azure.AI.FormRecognizer" publicKeyToken="..." culture="en-us" /> <bindingRedirect oldVersion="0.0.0.0-4.1.0.0" newVersion="4.1.0.0" /> </dependentAssembly>

You'll need to change the old and new versions to be 4.0.0.0. You'll need to do that for all the dependencies you downgrade as well. Be aware that sometimes a Nuget version doesn't match the assembly version. You have to use the assembly version. You should search the remaining sections of the config file to see if the assembly is referenced elsewhere as there may be additional references to the versioned assembly you need to update.
Please sign in to rate this answer.
Diallo, Mouhamadou S 0 Reputation points

2024-01-30T18:26:55.07+00:00

Hi Michael Taylor,

I'm currently using Azure.AI.FormRecognizer 4.1.0 in my visual studio project (I've attached below my app.config file to show you the assemblies versions that I'm currently using). However, this is throwing below error.
packages.config.txt

Thanks & Regards,
Mouhamadou

Michael Taylor 51,341 Reputation points

2024-01-30T19:15:01.4633333+00:00

You attached the packages.config which identifies what packages you're relying on. This isn't the app.config that is used for binding redirects. Based upon your packages.config you are relying on DS 6.0.0.1 but the fact that your app is trying to load 6.0.0.0 tells me your binding redirect is wrong. As I mentioned earlier, open your app.config file and find the binding redirect list. Looking for the DS assembly in that list and ensure it has the oldVersion set to 0.0.0.0-6.0.0.1 and newVersion set to 6.0.0.1 and then rebuild your app. Note that you might be getting a warning in the build about a mismatch. In that case you can double click the error in Error List and it'll auto-generate the binding redirect for you.

You might also consider going to the output directory of your executable and ensure the version of the assembly is 6.0.0.1. If it isn't then you have multiple outputs using different versions of the same package and that will cause problems. Use Manage NuGet Packages for Solution in Visual Studio and then look to see if there are any entries under the Consolidation tab. If so then consolidate any mismatches so all projects are using the same package versions.

Diallo, Mouhamadou S 0 Reputation points

2024-01-30T21:03:44.9233333+00:00

Michael Taylor, here is the app.config file. Thanks

app.config.txt

Michael Taylor 51,341 Reputation points

2024-01-30T21:15:33.0466667+00:00

The config has the binding redirect for 6.0.0.1 so that is the version it should load. First, do a rebuild of the solution.

Verify that the binary in the output directory of your executable is 6.0.0.1.

Verify that the .exe.config file that is generated has the binding redirect in it. It should but if you also happen to have autogenerate binding redirects enabled then something could stomp on it.

Check the remainder of the config file (and anything else that might dynamically load assemblies) and ensure there are no references to 6.0.0.0. For example there might be a diagnostic listener in your config looking for the binary.

Diallo, Mouhamadou S 0 Reputation points

2024-01-30T21:46:02.2+00:00

Hi Michael Taylor,
Here is the exe.config that is generated after rebuild and I verified that the binary in the output directory of my executable is below. I don't see any reference to to 6.0.0.0.

Captiva-AzureAnalyzeDocument.dll.config.txt

Below are all my installed packages.

Thanks & Regards,
Mouhamadou

Michael Taylor 51,341 Reputation points

2024-01-30T22:03:42.03+00:00

The file you posted is for a class library, not an executable. Class libraries don't have config files that are used at runtime. If your project is being hosted by another process then can you clarify what that process is? The process needs the binding redirect, not your class library.

Diallo, Mouhamadou S 0 Reputation points

2024-01-31T12:50:31.7633333+00:00

Hi Michael Taylor,

My project is a class library which will be used within the OpenText Captiva application Emc.InputAccel.CaptureClient which I didn't generate (it comes with the Captiva install), so I just reference in my class library project in visual studio. Maybe if we have a quick meeting I can show you the application in visual studio?

Thank you, Mouhamadou

Michael Taylor 51,341 Reputation points

2024-02-01T04:20:29.35+00:00

Sorry for the delay. I tried to get a trial version of the tool you're talking about so I can see what they are doing. But I haven't been able to. Since your code is hosted in a separate process then you're ultimately limited by whatever runtime requirements they have if they host your library directly in process, which is what it sounds like. This is one of the limitations of doing things that way.

But there are some things you should take a look at to see if there are workarounds.

Do you copy all your binaries (including dependencies) into some dedicated directory on the client? If so then it would seem like you should be able to load up your assemblies but if they have already loaded an assembly then your version won't be used. The error you're seeing could be caused by them having a binding redirect to v6 whereas you're using v6.0.0.1. You could check the app's config file to see.

Some reading I was doing seems to indicate a way to define your dependencies in their tool. I cannot confirm this but maybe there is some additional setup you need to do in the client tool (or a manifest file or something) in order for them to support loading the newer assembly.

You might need to post your question in their forums to see what they say. I don't believe the issue is related to .NET or the build at this point. It is a runtime binding issue which is controlled by their client.

Diallo, Mouhamadou S 0 Reputation points

2024-02-01T05:28:45.1733333+00:00

Hi Michael Taylor,

I think you are right because I have tested the same script outside the process and it works. I had a meeting with OpenText support yesterday morning and they said they will retest their library on their side, I've sent them my project.
I will let you know their findings.

Thanks,
Mouhamadou

Diallo, Mouhamadou S 0 Reputation points

2024-02-22T15:17:57.31+00:00

Hello,
This can be marked as resolved. The OpenText support had me change their codeClient.exe.config file to use the same DLL references as my VS project.
Thank you, Mouhamadou

Michael Taylor 51,341 Reputation points

2024-02-22T15:22:16.6+00:00

To "resolve" this you should mark one of the answers as the answer. Thanks.
Sign in to comment

Share via

I keep having issues with the dependent assemblies of Azure.AI.FormRecognizer.4.1.0 in visual studio c# project

WARNING! There was an error parsing the document

1 answer