Sqlite and other packages: Mono is not supported #351
Comments
|
@borgdylan I was noticing this too. We should be targeting portable profiles 7 (net45+win8) or 111 (net45+win8+wpa81) if we want to support Mono. We'll loose some types in the following contracts, but I don't think it should affect us too much.
|
|
Discussed in team triage - When running on full .NET we require net451 because we type forward System.Data.Common to types in the framework. We had API changes in 451 to allow this to work. We should see if we can get these changes reflected in Mono too. |
|
Some of those APIs may already be in mono. They need to support net451 as a new framework version. |
|
The mono devs have told me that their net45 is equal to net451. |
|
This may be a KRuntime issue, closing this issue for now. |
|
(See aspnet/dnx#374) |
anpete
pushed a commit
to anpete/EntityFramework
that referenced
this issue
Oct 24, 2014
…ts in detached entity) See issue dotnet#351. When an entity is in the Added state it means that it doesn't exist in the database and should be inserted during SaveChanges. If the state is then changed to Deleted this would mean delete an entity that doesn't exist in the database, which will fail. In the EF6 stack we instead detach the entity in this case so that it is just never inserted. This change implements the same behavior in EF7.
natemcmaster
pushed a commit
that referenced
this issue
Oct 31, 2018
They would eventually get freed with the connection, but this will free them sooner when an undisposed reader is finalized and the connection is still open. Fixes #351
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please consider changing net451 into net45 to allow the assemblies for SQLite etc. to be used under mono.
The text was updated successfully, but these errors were encountered: