The located assembly's manifest definition does not match the assembly reference. ExcelMapper depends on >= 6.0.0 - NPOI depends on SharpZipLib >= 1.3.2Ĭould not load file or assembly ', Version=1.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies. However, the problem persists with three nugets. Removed all binding redirects and disabled auto-generation of binding redirects. FusionLog only tells me a file is missing and does not specify anything further. Clearing all caches with dotnet nuget locals all -clear and mage.exe -cc - Reinstalled all nugets with update-package -reinstall - FusionLog tells me less than Windows event log, which is included in the original post. Solution structure (current)- A dummy console application project - Library Project 1 - Library Project 2and so on for another 35 timesĪs per suggestions in this post, I've tried following things: - Emptying Release and Debug folders under bin and obj. Post-build xcopy copies resulting files to the extensions folder. While each project has varying kinds of NuGet dependencies, the versions are managed on the solution level to ensure there are no conflicting versions.Īs suggested in this post, I also attempted to solve the issue by adding a startup project, which refers the libraries. Solution structure (original) - Library Project 1 - Library Project 2 and so on for another 35 timesĮach project has same build output path, which is an extensions folder of a proprietary application. Let's try this again, this time with what has been tried so far as per comments in this post. What else do I have to do to get rid of this bane of my existence? I have also ensured that all projects have bindingRedirect set. I have used the NuGet package manager on the solution to ensure all projects use same version of nuget. This inconsistency is downright driving me nuts. Yet at the same time many other dependencies works just fine, such as MySql.Data 8.0.21 depends on Bounc圜astle 1.8.3.1 or higher, and I have 1.8.9 and it works fine. Yet I get this exact same error if I dare to update to 1.3.3. For example, NPOI 2.5.5 depends on SharpZipLib 1.3.2 or higher. I also get same error with various other nugets if I am too eager with updating them. I even tried to downgrade to 5.0.0 and still getting same error. Just last December I was using version 5.0.0 and CsvHelper worked just fine. In each project that depends on, I have bindingRedirect set in app.config. Which means 1.0.0 or higher according to Microsoft docs, this is further confirmed by Visual Studio NuGet package manager. I've double-checked CsvHelper.csproj, and there it says exactly This is very weird, because the nuget specifically wants 1.0.0 or higher. "Could not load file or assembly ', Version= 1.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies. When a project attempts to use CsvHelper, I get following error. The latest version at the time of writing this is 27.2.1 and it depends on >= 1.0.0 and the version used by projects is 6.0.0. Today's repeating issue concerns CsvHelper nuget. Typically this works just fine, but one particular issue plagues me way too often and I would like to find a solution, if there is one. Nugets used by the projects vary a lot and I need to ensure all dependencies across the entire solution refer to same nuget version. I have a solution which encompasses about 37 projects, all of them output their binaries into same directory.
0 Comments
Leave a Reply. |