This question is quite old, and I had the same error message recently with Azure DevOps Yaml pipelines and Dotnet Core 3.1.
Also note that the public key and culture are important and dotPeek also show this information. dotPeek says it is 4.2.1.0 and that is the version that works correctly in our software.
#Post haste def windows
Windows explorer says the file is 5.06, nuget says its a 5.0.0.0 file. So for example, the correct binding for this file is the following: The assembly name listed in dotPeek is always accurate in my experience. The only way to get correct version info is to analyse the file itself. Windows properties is not always accurate and nuget is also not always accurate. However, that's only part of the problem - you need to know the correct version of the assembly file that you're using. If not, add any missing binding redirects that the package console missed.Ī general answer to this kind of issue is to use binding redirects as in other answers. Run your application and see if it works properly.All necessary binding redirects are generated.Type in Package Manager Console: Add-BindingRedirect.Remove all assembly binding content in web.config / app.config:.Is possible you have a wrong nugget versions in assemblyBinding try: Note that you'll have to enable logging by setting the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fusion\EnableLog registry key to 1. Microsoft has information about this tool here. If you still can't figure out where the old version is coming from, you can use the fuslogvw.exe application that ships with Visual Studio to get more information about the binding failures. (See my answer to this question for notes on creating a batch file to do this for you) This Microsoft article states that assemblies found in the GAC are not copied locally during a build, so you might need to remove the old version before doing a rebuild all. This will display the version number in the list of results, so you can see where the old version might be coming from.Īlso, like Lars said, check your GAC to see what version is listed there. Once you have a list of results, do View->Choose Details. First, use Windows file search to search your hard drive for your assembly (.dll). You can do a couple of things to troubleshoot this issue.
Is there any tool to search for this old versioned assembly? I look in my references, and I only have a reference to Utility version 1.2.0.203 (the other one is old).Īny suggestions on how I figure out what is trying to reference this old version of this DLL file?īesides, I don't think I even have this old assembly on my hard drive. The located assembly's manifest definition does not match the assembly reference. System.IO.FileLoadException: Could not load file or assembly 'Utility, Version=1.2.0.203, Culture=neutral, PublicKeyToken=764d581291d764f7' or one of its dependencies. (Exception from HRESULT: 0x80131040)**Īt x.Foo.Foo2(String groupName_) in Foo.cs:line 123Īt x.() in FooTests.cs:line 98** System.IO.FileLoadException: Could not load file or assembly 'Utility, Version=1.2.0.200, Culture=neutral, PublicKeyToken=764d581291d764f7' or one of its dependencies. I am trying to run some unit tests in a C# Windows Forms application (Visual Studio 2005), and I get the following error:
0 kommentar(er)
