Ladislav Mrnka

My feedback

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

    We’ll send you updates on this idea

    Ladislav Mrnka commented  · 

    IMHO it is not needed. Classes generation process for both reverse engineering and DbContext generator can be changed directly in T4 template. Making those properties virtual is an easy change. If you have a problem with it ask a question on Stack Overflow and community will help you.

    Moreover change tracking proxies are not considered as default solution anymore:
    http://blog.oneunicorn.com/2011/12/05/should-you-use-entity-framework-change-tracking-proxies/

  2. 117 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Ladislav Mrnka shared this idea  · 
  3. 69 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Ladislav Mrnka commented  · 

    @mabster: In such case it is a time to define reusable extension method for your context which will wrap your eager loading call ...

    I don't say that possibility to statically define eager loading is not useful - for example last paragraph in proposal makes it valid requirement but some scenarios can be simply solved by common development techniques without any change to framework.

  4. 94 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Ladislav Mrnka commented  · 

    Milan: POCO designer = class diagram supported in all versions of VS. Also I don't agree with your mentioned strength of visual modeling. Visual modeling has its limitation and the good code is the best description of model.

    Ladislav Mrnka commented  · 

    This is now available in Entity Framework Power Tools CTP1. There is possibility to create read only EDMX diagram from your code first model (your current mapping configuration).

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

    We’ll send you updates on this idea

    Ladislav Mrnka commented  · 

    Entity is just class and you are responsible for initializing internals of your classes - it is not a workaround to assign list in your constructor (or directly as initializer). It is common and correct practice. As @Diego mentioned EF cannot handle instantiation of your classes if you use new keyword because there is no EF involved. Try to use Create method on your DbSet instead and if you have class enabled for lazy loading you will get collections initialized.

  6. 2 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Ladislav Mrnka commented  · 

    Opposite of Materialized event is SavingChagnes (or override SaveChanges). You just don't have the event for each object. You have it for all of them and you must find objects you are interested in the event handler (through ObjectStateManager).

  7. 78 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Ladislav Mrnka commented  · 

    This is already implemented you just need to call user.Cars.CreateSourceQuery().Count() where Cars must be EntityCollection<Car>.

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

    We’ll send you updates on this idea

    Ladislav Mrnka commented  · 

    I like this too but I see it more like scenario for custom converters where you load XML/string and instead of loading it to string property you will provide custom converter to fill an object.

  9. 107 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Ladislav Mrnka commented  · 

    This request doesn't make sense. There is no streaming between database and application except FILESTREAM which works only per record and requires two different queries - it would be a very special type of per column lazy loading but it will be SQL Server only.

  10. 818 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Ladislav Mrnka commented  · 

    "Without having to manage database objects - linked servers ..." That is totally out of scope of ORM. You should always have to do that even if cross database mapping will be supported. There is a big difference between cross database and cross server queries.

  11. 3 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Ladislav Mrnka commented  · 

    If you need to know context from your entity you should make review of your architecture. Entity should not know expose context because it is not its responsibility. It should even not know about context existence (POCO).

  12. 101 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Ladislav Mrnka commented  · 

    .NET framework has big support for tracing so I cannot understand how could such elementary feature be omitted. ADO.NET team should really check how their colleagues in other teams preparing their API. Especially they should talk with WCF team where logging and extensibility was taken seriously.

    Ladislav Mrnka supported this idea  · 

Feedback and Knowledge Base