This project is read-only.


Consider adding Ignore method directly on lightweight property configurations


This is based on customer feedback located here.

The idea is to enable doing something like this:
    .Where(p => p.GetCustomAttribute<ColumnAttribute>() == null))
    .Configure(p => p.Ignore());
Instead of having to do something like this:
    .Configure(conf => conf
        .Where(p => p.GetCustomAttribute<ColumnAttribute>() == null)
        .ForEach(p => conf.Ignore(p)));
Closed Dec 12, 2016 at 10:31 PM by RoMiller
EF Team Triage: We are transitioning this project to GitHub ( As part of this transition we are bulk closing a large number of issues in order that our new issue tracker will accurately reflect the work that our team is planning to complete on the EF6.x code base.

Moving forwards, our team will be fixing bugs, implementing small improvements, and accepting community contributions to the EF6.x code base. Larger feature work and innovation will happen in the EF Core code base ( Closing a feature request in the EF6.x project does not exclude us implementing the feature in EF Core. In fact, a number of popular feature requests for EF have already been implemented in EF Core (alternate keys, batching in SaveChanges, etc.).

This is a bulk message to indicate that this issue was closed and not ported to the new issue tracker. The reasons for not porting this particular issue to GitHub may include:
  • It was a bug report that does not contain sufficient information for us to be able to reproduce it
  • It was a question, but sufficient time has passed that it's not clear that taking the time to answer it would provide value to the person who asked it
  • It is a feature request that we are realistically not going to implement on the EF6.x code base
    Although this issue was not ported, you may still re-open it in the new issue tracker for our team to reconsider ( We will no longer be monitoring this issue tracker for comments, so please do not reply here.


MassoudMario wrote Jun 29, 2013 at 1:41 PM

Hi, that will be a nice feature if it will be included, specially in large, enterprise code-first models.

shrazaghi wrote Jun 30, 2013 at 9:48 AM

in code-first model this will be very useful pattern, and more understandable.

RoMiller wrote Jul 3, 2013 at 11:17 PM

EF Team Triage: We agree that this would be good to enable. Given we are closing down the EF6 release we're moving it to the Future release to re-triage after EF6.