How to debug System.TypeLoadException errors in .NET?

I'm getting the following error on one of my referenced assemblies:

Could not load type 'System.Func`2' from assembly 'MyAssembly, ...

My first instinct was to see what MSDN had to say about it:

TypeLoadException is thrown when the common language runtime cannot find the assembly, the type within the assembly, or cannot load the type.

It appears to be is saying that the CLR simply can't find the type? That might make more sense if this wasn't something that was in mscorlib. This was all built on top of .NET4 with VS2010, so there's no mono or other weird library issues. What's goin开发者_StackOverflowg on?

I received this error after refactoring. I had two projects compiling to DLLs with the same name.

Check the "Assembly name" in the project's properties' "Application" section.

The problem is that you have a mismatch in your versions. Make sure all your assemblies are compiled for .NET 4.

I'm not sure about your specific scenario, but the Assembly Binding Log Viewer (fuslogvw) is usually very helpful in debugging type load issues. More details at http://msdn.microsoft.com/en-us/library/e74a18c4.aspx

You may also get this if you change the assembly you're trying to load but still have an old version in the GAC. It tries to load the GAC'ed version not what you reference in your VS project.

I got this error when I moved a class from one project to another in a cleanup effort. After looking at all other possible reasons, reloaded each of the projects in my solution and everything worked.

1. Right Click on the project name in solution explorer
2. Select Unload Project
3. Right Click on the project name in solution explorer
4. Select Reload Project

This problem may occur if you have different versions of NuGet packages installed across different projects. To identify these cases,

1. Right-click the solution in Solution Explorer and select "Manage Nuget Packages for Solution"
2. Select the "Consolidate" tab
3. For any identified packages, identify the version you want and click "Install" to consolidate the package to that version.

I encountered this exception when I refactored to move some classes to their own library, and referenced a different version of the library it's trying to load in the new library (acquired with NuGet) than I had been using in the original project.

The thing that fixed it was to open the NuGet Manager in the old project, and update the appropriate package to be the same version I was using in my new library.