Entity Framework Core 1.0 You should just need to update the tools section of your project.json file to include this: “Microsoft.EntityFrameworkCore.Tools”: { “version”: “1.0.0-preview1-final”, “imports”: [ “portable-net45+win8+dnxcore50”, “portable-net45+win8” ] } This should make the dotnet ef commands available. Important I should also note here that the dotnet ef commands will only be available when running … Read more
From a point of view of clean creation of POCO entities, there is no difference between the two generators. Both generators produce the same entities, however, ADO.NET POCO Entity Generator is based on ObjectContext‘s API, whereas ADO.NET DbContext Generator is based on DbContext‘s API. DbContext’s API has a few very nice new features (Local, Query … Read more
This is an option: dbContext.Entry(entity).State = EntityState.Detached;
If you talk about dynamic proxies in EF there are two different types to distinguish: Proxies for lazy loading Proxies for change tracking Usually a change tracking proxy also can serve as a proxy for lazy loading. The reverse is not true. This is because the requirements for change tracking proxies are higher, especially all … Read more
There a few things you need to change inside the .tt file. I choose to use the third solution you suggested but this requires to be formatted like FK_CollectionName_RelationName. I split them up with ‘_’ and use the last string in the array. I use the RelationName with the ToEndMember property to create a property … Read more
Turns out that Entity Framework will assume that any class that inherits from a POCO class that is mapped to a table on the database requires a Discriminator column, even if the derived class will not be saved to the DB. The solution is quite simple and you just need to add [NotMapped] as an … Read more
The problem is that your Person entities are still attached to context created in GetPersons. If you want to work with attached entities you have to use same context instance in both select and update operations. You have two choices to solve your problem. 1) Correctly handled attached entities public class Program { [STAThread] static … Read more
[ UPDATE : for an easier solution that works with Visual Studio 2013 Update 4 (Pro and Ultimate) and recent versions of Sqlite Providers and EF, look at the solution ‘broslav’ posted below. Don’t know if it works with Express editions… ] Ok, this is a suggestion. This does NOT work for Visual Studio Express … Read more
If you don’t want to execute SQL directly, the best way is to use Any(). This is because Any() will return as soon as it finds a match. Another option is Count(), but this might need to check every row before returning. Here’s an example of how to use it: if (context.MyEntity.Any(o => o.Id == … Read more
If your migration does not work correctly try to set Database.Initialize(true) in DbContext ctor. public CustomContext(DbConnection connection) : base(connection, true) { Database.Initialize(true); } I have similar problem with migrations. And in my solution I have to always set database initializer in ctor, like below public CustomContext(DbConnection connection) : base(connection, true) { Database.SetInitializer(new CustomInitializer()); Database.Initialize(true); } … Read more