Skip to content
This repository has been archived by the owner on Dec 18, 2017. It is now read-only.

Wrong EntityFramework is being loaded at runtime on mono #511

Closed
d0apga opened this issue Aug 7, 2014 · 7 comments
Closed

Wrong EntityFramework is being loaded at runtime on mono #511

d0apga opened this issue Aug 7, 2014 · 7 comments
Assignees
Milestone

Comments

@d0apga
Copy link

d0apga commented Aug 7, 2014

when use entityframework7 in mono,rolysn compiler use the old entityframework6 dll in mono's lib folder,it should use kpm downloaded packages.

@davidfowl
Copy link
Member

When running you mean not restoring right? Can you provide a repro project??

@d0apga
Copy link
Author

d0apga commented Aug 7, 2014

it seems that restoring correctly,but not use the restore package.
i push the demo source to my repo: https://github.com/nidilong/aspnetvnextdemo.git,
thanks a lot.

@davidfowl
Copy link
Member

So this bug title is incorrect, you mean that the wrong EntityFramework is being loaded at runtime.

@d0apga d0apga changed the title not use kpm restore packages when compile aspnet vnext projects in linux Wrong EntityFramework is being loaded at runtime Aug 7, 2014
@d0apga
Copy link
Author

d0apga commented Aug 7, 2014

oh,I'm sorry. Thanks @davidfowl

@davidfowl davidfowl changed the title Wrong EntityFramework is being loaded at runtime Wrong EntityFramework is being loaded at runtime on mono Aug 7, 2014
@borgdylan
Copy link

This used to happen to me as well. To work around it you must nuke the mono EF assemblies from the GAC and the lib/mono/4.5 directories.

@davidfowl
Copy link
Member

The version of the assembly should be different and we aren't passing in the full assembly identity so it might be a problem with how loading works on mono. I'll take a look.

@borgdylan
Copy link

In my case it happened because mono has EF 6.0 and I am using EF 6.1.1. The assemblies in both cases use the same version metadata.

@davidfowl davidfowl added this to the 1.0.0-alpha4 milestone Aug 19, 2014
@davidfowl davidfowl self-assigned this Aug 19, 2014
davidfowl added a commit that referenced this issue Aug 19, 2014
- Turns out mono's 4.5 profile (for the versions of mono we support)
is actually compatible with .NET 4.5.1.
- Fix problem with compiling against reference assemblies
that were not resolved via dependency resolution.

#511
#374
davidfowl added a commit that referenced this issue Aug 19, 2014
- Turns out mono's 4.5 profile (for the versions of mono we support)
is actually compatible with .NET 4.5.1.
- Fix problem with compiling against reference assemblies
that were not resolved via dependency resolution.

#511
#374
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants