Jorge

My feedback

  1. 369 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Jorge supported this idea  · 
  2. 865 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Jorge supported this idea  · 
  3. 137 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    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.

    Jorge commented  · 

    This is also needed in case you want to use an IoC container to create each entity!

    Jorge supported this idea  · 
  4. 408 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Jorge supported this idea  · 
  5. 118 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    started  ·  Mark Stafford responded

    As part of the OData v4 client library, we plan to modify our code generation from using CodeDom to a T4 template. Best case scenario, in the same time frame we will make that T4 template publicly available and anyone can modify it to their heart’s content. Worst case scenario, we will make the T4 template public as soon as we can.

    Jorge supported this idea  · 

Feedback and Knowledge Base