For me it has been kind of unexpected behavior. When I update NuGet package, I get newest Entity Framework binaries. Today it is version 5.0. However, default MVC template targets .NET version 4.0. Newest version of Entity Framework for .NET 4.0 is 4.4. The NuGet package contains both assemblies, but the project will use 4.4 because the project targets .NET 4.0 by default. Furthermore, simply changing target runtime version in project properties is not enough. What finally has worked for me was manually editing .csproj
file. I located assembly reference in XML and changed path in HintPath
tag from \lib\net40\EntityFramework.dll
to \lib\net45\EntityFramework.dll
. The conclusion is to pay close attention to what particular version of assembly is actually being referenced and not relying only on NuGet versioning.