Martin

My feedback

  1. 40 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Martin supported this idea  · 
  2. 74 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Martin supported this idea  · 
  3. 348 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Martin supported this idea  · 
  4. 22 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Martin commented  · 

    It would be nice to have auditing not dissimilar to https://github.com/loresoft/EntityFramework.Extended/wiki/Audit-Log, but much more flexible and robust. The major issue with it is lack of audit tracking for many-to-many relationships.

  5. 965 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Martin commented  · 

    Please stop reviewing and just get this done. There are so many problems with the providers offered by http://code.msdn.microsoft.com/EFProviderWrappers-c0b88f32 when using CodeFirst, particularly if you are doing a multi-tenant application with a DB per tenant scheme as I am doing, using migrations.

    And yes, for Azure Database, performance is a serious concern where caching is critical. Having to ad-hoc cache at all the various points where we want to cache is too painful. At least some out of the box extension points for caching should be a no-brainer.

    Martin supported this idea  · 
  6. 500 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  Mark Stafford responded

    While this ask is purely a feature ask, we currently do not generate methods on the client to call service operations. 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 either add this feature ourselves down the road or make the T4 template public as soon as we can.

    Martin supported this idea  · 
  7. 1,081 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    started  ·  Mark Stafford responded

    Good news: this is coming – and not just on entity types but on complex types as well. Enums are part of the OData v4 protocol. In fact, it was one of the things we argued vociferously for precisely because of the number of votes on this issue.

    Martin supported this idea  · 
  8. 11 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Martin supported this idea  · 

Feedback and Knowledge Base