Could not load file or assembly crystaldecisions crystalreports engine dll

#Could not load file or assembly crystaldecisions crystalreports engine dll .dll#
#Could not load file or assembly crystaldecisions crystalreports engine dll update#

Yet there were otherВ packages in the solution like В which depended on old versions of the updated packages.

#Could not load file or assembly crystaldecisions crystalreports engine dll update#

A newВ Nuget package reference trigerred the update of several other packages. So despite the fact that my web api project had an explicit reference to 5.2.2.0, after compilation, its assembly manifest had an additional reference to .5.1.0.0.Д«ut let's not forget how all this was brought about. And thisВ was built with a specific version reference to 5.1.0.0. In my case, my web api project was referencing 5.2.2.0 but it was also referencing an.

#Could not load file or assembly crystaldecisions crystalreports engine dll .dll#

dll manifest will contain a reference to the specific version of Assembly 2. It turns out that if your project has a reference to some external Assembly 1 and this external Assembly 1В has a reference to a specific version of an Assembly 2, then your project. dll was referencing and thus requiring two different versions of ? All my other projects in the solution were referencing the correct 5.2.2.0 version of. The assembly manifest showed the same thing.

I had serveral references to and one of them was version 5.1.00. csproj in the text editor to see if the references were correct. I did not trust the VS properties window, so I manually inspected all the. The first thing I checked was that all projects in my solution were referencing 5.2.2.0 and not 5.1.0.0: The located assembly's manifest definition does not match the assembly reference. dll (note: without the Web.config), ran the web api project and got the following error:Д¬ould not load file or assembly ', Version=5.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. In other words I made sure that if for example Project 1 referenced the from the Newtonsoft.Json.6.0.6В package and Project 2 had a reference to the, Project 2 referenced it from the same 6.0.6 package and not an earlier version.ДЄt one point in my main web api project I hadВ to add a reference toВ the following package:В .5.2.2.В This triggered an update of all the dependencies of theВ .5.2.2 among which wasВ . All the nuget packages in the solution were managed with extreme care, so that there were no versioning indescrepancies between same references in different projects. I had a solution with an ASP.NET Web Api project and several library projects, which were referencedВ by the web api. So in this article I will walk you through aВ scenario where I encountered this versioning error and how I solved it. Understanding why this works is nowhere explained, at least I could not find it. There are numerous posts about this error (just searchВ stackoverflow), and most users seem to solve this problem by just running the nuget update-package command in Visual Studio, which updates all theВ packages and refenreces in the Visual Studio solution. But fixing it is not so straight-forward. System.IO.FileLoadException : Could not load file or assembly '., Version=., Culture=neutral, PublicKeyToken=.' or one of its dependencies. Thus you might thinkВ no GAC, no versioning problems. Then Nuget came along and one thing was sure.

It more failed than succeeded in doing so. NET tried to solve the so called DLL HellВ with its GAC and versioning.