Entity Framework 6 NotMapped attributes

Question

Is there a way using the fluentAPI within a DbContext to manually include ICollections that have been [NotMapped] in the model? I know how to manually ignore properties using the fluentAPI

modelBuilder.Entity<MyEntity>().Ignore(e => e.MyChildCollection);

But if the property was defined with the [NotMapped] attribute (see below), can it be "brought back" into the model?

[NotMapped]
public virtual ICollection<ChildEntityType> MyChildCollection { get; set; }

score 0 · Answer 1 · answered May 14 '15 at 11:16

0

Yes it can be. You just have to remove the [NotMapped] Data Annotation and then go to your Package Console Manager. Type add-migration [anyname]. Then type update-database. It will automatically make the changes.

answered May 14 '15 at 11:16

TJ Riceball

240
1
2
11

I'm not actually looking to update the database. We are making all updates to the database directly and not relying upon Entity Framework to update the DB. The way our system is structured, not all models defined for the database tables are referenced by the DLL containing the DbContext objects. We would like all "ICollection" child collections marked as [NotMapped] by default and then explicitly include them in the DbContext model in the "OnModelCreating" override method of the DBContext. I hope that clarifies. – Ted May 14 '15 at 14:39

Entity Framework 6 NotMapped attributes

1 Answers1