Entity Framework Core Feature Suggestions

Welcome! Use this web site to submit ideas and vote for what features you want to see in future versions of Entity Framework Core.

Our team will only fix bugs, implement small improvements and accept community contributions in the EF6 codebase. Larger feature work and innovation will happen only in the EF Core codebase. If you have ideas for improving EF6, we recommend you submit them on the EF6 GitHub site listed below.

Please also consider these other options before submitting anything to this site:

  • If you want to learn how to use our products, visit our documentation pages.
  • If you want to report bugs, make contributions, or learn about our product roadmaps, visit our EF Core or EF6 project pages on GitHub.
  • If you have technical questions or need help, try StackOverflow’s EF Core or EF6 tags. Note that roadmap questions, bug reports, feature requests or ideas are not appropriate for StackOverflow. Visit StackOverflow’s help center for guidance on appropriate usage.

How can we improve Entity Framework Core?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  1. Custom type mapping and type conversion support

    Currently the only conversion available in EF Core libraries 4.5 and EF 5.0 are enums mapped to integers but that is only tip of the iceberg. There is whole big feature behind - simple type mapping or conversions defined directly in mapping.

    For example what if my database contains char column with Y, N values and I want to map it to bool property directly without any additional stuff doing the conversion inside my entity? Or more complex example - what if my column contains value like en-us and I want to map it to instance of CultureInfo? There are…

    1,364 votes
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)

      We’ll send you updates on this idea

      78 comments  ·  Flag idea as inappropriate…  ·  Admin →
    • Eager loading for properties of derived classes

      In entity framework there should be a way to eager load (include) navigation properties of a derived class.

      When in an data model for entity framework has a navigation property it is not posseble to eager load that navigation property besides when using OfType<> or when eager loading the derived type itself by a navigation property.
      This could be done by using a special syntax of the include path.
      Since a property of the base class can not have the same name as the derived class, it would also be possible to navigate to the derived class by its name.

      324 votes
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        Signed in as (Sign out)

        We’ll send you updates on this idea

        22 comments  ·  Flag idea as inappropriate…  ·  Admin →
      • EF Core Migrations Column ordering

        Migrations on EF Core should do Scaffolding of the fields of entity like the order of the entity (and NOT alphabetical)

        As this req:
        https://github.com/aspnet/EntityFramework/issues/2272
        and
        https://github.com/aspnet/Scaffolding/issues/398

        141 votes
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          Signed in as (Sign out)

          We’ll send you updates on this idea

          11 comments  ·  Flag idea as inappropriate…  ·  Admin →
        • Decouple entity creation in EF and support entities without default constructors and publically settable properties

          EF should decouple the implementation of the entity objects from the mapping functionalities. The EF team could provide the current entity creation as a default variant which can be attached to the mapper. The developer has the option to provide it's own data transfer object layer. Therefore we need to abstract the entities through interface usage an a generic naming schema (dot notation of an object model like Person.Name). So the EF would be much more flexible to use.

          Note by Diego Vega: I am merging this idea with a few other ideas that are approximately equivalent but extend in…

          138 votes
          Sign in
          Check!
          (thinking…)
          Reset
          or sign in with
          • facebook
          • google
            Password icon
            Signed in as (Sign out)

            We’ll send you updates on this idea

            11 comments  ·  Flag idea as inappropriate…  ·  Admin →

            This feature is at least partially implemented in EF Core 2.1. There is no custom binding but many additional patterns are now supported by convention, including injecting the property values in the constructor, injecting instances of services also in the constructor and on properties.

            Direct mapping to fields was already supported in 1.1.

          • Full Text Search

            Provide Full-Text Search capabilities similar to Lucene.Net-NHibernate

            127 votes
            Sign in
            Check!
            (thinking…)
            Reset
            or sign in with
            • facebook
            • google
              Password icon
              Signed in as (Sign out)

              We’ll send you updates on this idea

              4 comments  ·  Flag idea as inappropriate…  ·  Admin →
            • Code First support for user defined functions (UDFs)

              Similar to adding support for stored procedures in Code First, but for functions also.

              Using model first, this is supported and using EdmFunctionAttribute they can be used from LINQ to Entities. I really miss this in the Code First approach.

              See also: http://data.uservoice.com/forums/72025-ado-net-entity-framework-ef-feature-suggestions/suggestions/1607971-code-first-support-for-stored-procedures?ref=title

              78 votes
              Sign in
              Check!
              (thinking…)
              Reset
              or sign in with
              • facebook
              • google
                Password icon
                Signed in as (Sign out)

                We’ll send you updates on this idea

                5 comments  ·  Flag idea as inappropriate…  ·  Admin →
              • 73 votes
                Sign in
                Check!
                (thinking…)
                Reset
                or sign in with
                • facebook
                • google
                  Password icon
                  Signed in as (Sign out)

                  We’ll send you updates on this idea

                  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
                • SQL Variant support

                  I would like EF to support sqlvariant columns like Linq to SQL does

                  46 votes
                  Sign in
                  Check!
                  (thinking…)
                  Reset
                  or sign in with
                  • facebook
                  • google
                    Password icon
                    Signed in as (Sign out)

                    We’ll send you updates on this idea

                    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
                  • Add DbContext.Database.SqlQuery to Entity Framework Core

                    I can't always get the best performance for extremely specific queries queries in Entity Framework. Sometimes it is best to just write very specific SQL (Currently working on a CTE recursive query that I wouldn't even know how to begin getting into EF without hitting the DB multiple times). Having SqlQuery<T> available give me complete freedom and allows me to use EF in the same way as Micro ORMS like Dapper to map a specific DTO when it makes sense. I don't wan't to have to map a custom object to my context and use the FromSql implementation off of…

                    37 votes
                    Sign in
                    Check!
                    (thinking…)
                    Reset
                    or sign in with
                    • facebook
                    • google
                      Password icon
                      Signed in as (Sign out)

                      We’ll send you updates on this idea

                      6 comments  ·  Flag idea as inappropriate…  ·  Admin →

                      The plan is to support this in EF Core 2.1 but with a small variation. The feature is called query types and the idea is that these are types that are added to the model (e.g. they are not ad-hoc) and however they don’t need to have entity keys and they don’t need to be mapped to a table. On of these query types is defined in the model it can be used in ad-hoc queries, e.g. context.Query().FromSql(“SELECT …”);

                    • Ability to map any serializable object to XML, JSON or binary columns

                      For example a database table could have a [Settings] column of type xml. And a mapped entity type could have a property [Settings] of some serializable type. Then you will be able to read and write data into and from this [Settings] column with EF. Like this:

                      var user = db.Users.First(x => x.ID == 1);
                      if (user.Settings == null)
                      {
                      user = new Settings();
                      }
                      user.Settings.ProductsPerPage = 20;
                      db.SaveChanges();

                      37 votes
                      Sign in
                      Check!
                      (thinking…)
                      Reset
                      or sign in with
                      • facebook
                      • google
                        Password icon
                        Signed in as (Sign out)

                        We’ll send you updates on this idea

                        3 comments  ·  Flag idea as inappropriate…  ·  Admin →
                      • Entity Framework support for Windows Store apps

                        System.Data.dll -- which is fundamental to EF -- is not available inside Windows Store Apps. Thus development of Windows Store apps is two steps back of where WPF and Silverlight development have been.

                        23 votes
                        Sign in
                        Check!
                        (thinking…)
                        Reset
                        or sign in with
                        • facebook
                        • google
                          Password icon
                          Signed in as (Sign out)

                          We’ll send you updates on this idea

                          4 comments  ·  Flag idea as inappropriate…  ·  Admin →

                          The upcoming EF Core 2.0.1 has been tested more extensively with UWP. It requires .NET Standard 2.0 support, which means it only works Windows 10 Fall Creators Update and later releases. EF Core 1.x versions only went through minimal testing with UWP and several issues were encountered, in particular when compiling with .NET Native.

                        • Result of Sum() of an empty set should be 0 rather than NULL in LINQ to Entities

                          Currently if an empty set is expected it is necessary to cast either the result or the input elements of Sum to Nullable<T> to compensate for the type mismatch between the SQL database and the signature of the methods in LINQ.

                          17 votes
                          Sign in
                          Check!
                          (thinking…)
                          Reset
                          or sign in with
                          • facebook
                          • google
                            Password icon
                            Signed in as (Sign out)

                            We’ll send you updates on this idea

                            6 comments  ·  Flag idea as inappropriate…  ·  Admin →
                          • Allow utilizing Dependency Injection for entity materialization

                            I would like to see EF upgraded to allow a user-selectable Dependency Injection container to manage materialization of entities. This would allow finer grained control over how objects are materialized, as well as support interface based definitions for entities.

                            10 votes
                            Sign in
                            Check!
                            (thinking…)
                            Reset
                            or sign in with
                            • facebook
                            • google
                              Password icon
                              Signed in as (Sign out)

                              We’ll send you updates on this idea

                              1 comment  ·  Flag idea as inappropriate…  ·  Admin →
                            • Support read-only mapping to tables without key

                              Allow mapping of database views without requiring the Key Attribute

                              When mapping entitis to Views, it´s common that no Key can be set, bescause the view does not provide it and you can´t map it. The idea is:

                              * Make it possible to map to Views (or tables) in a read only fashion that does not require the Key Attribute

                              10 votes
                              Sign in
                              Check!
                              (thinking…)
                              Reset
                              or sign in with
                              • facebook
                              • google
                                Password icon
                                Signed in as (Sign out)

                                We’ll send you updates on this idea

                                2 comments  ·  Flag idea as inappropriate…  ·  Admin →
                              • Encryption of Columns

                                Would be nice to be able to map encryption to a column. have a convention based or override using a
                                function (Func<>).

                                9 votes
                                Sign in
                                Check!
                                (thinking…)
                                Reset
                                or sign in with
                                • facebook
                                • google
                                  Password icon
                                  Signed in as (Sign out)

                                  We’ll send you updates on this idea

                                  1 comment  ·  Flag idea as inappropriate…  ·  Admin →

                                  This is something that we believe will be supported with the work on value conversions that we are doing in EF Core 2.1. There won’t be conventions and the application will have to take care of selecting an encryption algorithm and doing any key management, but it should be able to configure properties to be perform encryption before sending the values to a database column and to decrypt on the way back.

                                • Add the ability to persist TimeSpan values (and others) as strings

                                  The immediate need is to be able to map between TimeSpan values on the CLR side and their equivalent string representations on the database side.

                                  Currently TimeSpan can only be mapped to the SQL time datatype, which does not make much sense since the time SQL type is meant for storing time-of-day while TimeSpan is meant to represent an arbitrary amount of time. Mapping between the two limits the TimeSpan to a 24 hours interval, which rarely makes sense.

                                  In our current DAL we do this by persisting TimeSpan values as strings, calling TimeSpan.ToString() on the way down and TimeSpan.Parse()…

                                  6 votes
                                  Sign in
                                  Check!
                                  (thinking…)
                                  Reset
                                  or sign in with
                                  • facebook
                                  • google
                                    Password icon
                                    Signed in as (Sign out)

                                    We’ll send you updates on this idea

                                    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
                                  • Don't see your idea?

                                  Entity Framework Core Feature Suggestions

                                  Feedback and Knowledge Base