![]() ![]() 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. The located assembly's manifest definition does not match the assembly reference. 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. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
September 2023
Categories |