Bug 20900 - Bundled EF6 conflicts with EF6.1.1 brought in from nuget
Summary: Bundled EF6 conflicts with EF6.1.1 brought in from nuget
Alias: None
Product: Runtime
Classification: Mono
Component: General ()
Version: unspecified
Hardware: PC Linux
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2014-06-26 07:18 UTC by Dylan Borg
Modified: 2016-08-09 12:56 UTC (History)
3 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Dylan Borg 2014-06-26 07:18:26 UTC
I was using ASP.NET vNext and I brought in the latest EF from nuget. When I compile the EF from nuget gets used but when I run mono overrides it with its old version. This means the assembly fails to load is I use any new APIs. The hack i found was to nuke the bundled ef from /usr/lib/4.5 and from the gac.
Comment 1 Dylan Borg 2014-06-26 08:46:55 UTC
This also happens for Npgsql. Mono is overriding assemblies loaded manually with its own.