could not load file or assembly acpdfcreatorlib.net.dll

Could Not Load File Or Assembly Accreatorlib.Net Dll Was Not
Could Not Load File Or Assembly Accreatorlib.Net Download Of New
Could Not Load File Or Assembly Accreatorlib.Net How To Resolve This

Could Not Load File Or Assembly Accreatorlib.Net Dll Was Not

But when I switch to release and compile everything ok(even using the 3rd party release dlls) it keeps telling me that the wrapper dll was not found.

An attempt was made to load a program with an incorrect format.

I work on a 64-bit Win7 pc and aparently if I use Any CPU as target it doest find the wrapper dll.

Now, lets look into possible solutions: Solution There are two solutions: Upgrade NuGet package of Lib C in Lib A to v2 Adding binding Redirect element in config file Lets see binding redirect solution first.

It is easy to resolve provided that the new assembly version is backward compatible.

Could Not Load File Or Assembly Accreatorlib.Net How To Resolve This

Before going into how to resolve this issue, lets understand how runtime locates the assembly.

If you just want to know the solution, you can skip this section, however, I recommend to go through it once to understand why we get this exception.

I am also referencing some library that is also using Newtonsoft.Json but with different version.

When you build solution there can be one Newtonsoft.JSON.dll in bindebug or binrelease folder.

Visual studio), run it from developers command prompt with admin privileges.

Here is sample log of probing (relevant parts are made bold ): LOG: This bind starts in default load context.

LOG: Using application configuration file: F:visual studio 2017ProjectsTestBindingAppTestBindingAppbinDebug TestBindingApp.exe.Config LOG: Using host configuration file: LOG: Using machine configuration file from C:WindowsMicrosoft.NETFrameworkv4.0.30319config machine.config.

LOG: Post-policy reference: Newtonsoft.Json, Version10.0.0.0, Cultureneutral, PublicKeyToken30ad4fe6b2a6aeed LOG: GAC Lookup was unsuccessful.

Could Not Load File Or Assembly Accreatorlib.Net Download Of New

LOG: Attempting download of new URL file:F:visual studio 2017ProjectsTestBindingAppTestBindingAppbinDebugNewtonsoft.Json.DLL.

LOG: Assembly download was successful.

Attempting setup of file: F:visual studio 2017ProjectsTestBindingAppTestBindingAppbinDebugNewtonsoft.Json.dll LOG: Entering run-from-source setup phase.

LOG: Assembly Name is: Newtonsoft.Json, Version11.0.0.0, Cultureneutral, PublicKeyToken30ad4fe6b2a6aeed WRN: Comparing the assembly name resulted in the mismatch: Major Version ERR: The assembly reference did not match the assembly definition found.

Probing terminated This log gives insights into how assembly is located.

More details are available at Microsoft Docs How runtime locates the assembly.

Below is summary: Determine the correct assembly version: appweb config, publisher policy and machine.config are examined for this.

Cached Assembly: Check the same assembly bound before then use it, if it failed then current request is failed immediately without any further steps.

GAC: Assembly is checked in Global Assembly Cache, it must be strongly named.

If not present, then probing is done in Application base considering culture, Name and private path of probing element.

The Application base is location from executable is run Then coming to question why error of assembly cannot be loaded It is failing in one of the above steps.

More often the first step the assembly is not found matching the version.

Consider the scenario: Lib A references Lib C v1 Lib B references Lib C v2 Lib A references Lib B Then after building the project there would be one version of Lib C in Application base so Lib A cant find other version.

Can you guess which version of Lib C would be present in Application base It is Lib C v1.

The reason is dependency resolver follows 4 rules Lowest applicable version (e.g.

Version 2.2 for 2.2 and if 2.2 is not available and 2.3 is next then 2.3) Wildcard (e.g.

Thus, this rule can result in a downgrade of the package version) Cousin dependency (lowest maximum version that satisfies all requirements.

This is case when different package versions are referred to at the same distance in the graph from the application).

We understood which version the application gets and how runtime probes it.

Could Not Load File Or Assembly Acpdfcreatorlib.Net.Dll