Home

Autocomplete not working when using SelectMany overload

I've tried googling this issue, but I may just be using the wrong terminology, so here's some pictures of what happens

when in linqpad, if use the selectmany overload that carries a grouping down with it, if i then try to project it into a new anon object, and then try to "dot" into the properties of one of the things i'm passing down (the initial level of intellisense works fine), instead of getting the actual properties, i get a "dbexpression"

image

the type is correct up in the selectmany

but down in the new select, i get this

image

however, when i do this in visual studio, the intellisense works fine

image


in both cases, the code runs correctly when i run it.


any idea why this is happening?



Comments

  • I can't reproduce this issue. I tried with both the emitted DataContext and my DbContext. What type is netlister? Are you running the most recent beta?

    LINQPad's intellisense is provided by third-party libraries. So I have experienced it behaving differently from Visual Studio's.
  • edited January 2015
    I stripped out all my extensions and such and found that it is now working, so it must be something dumb i configured. thanks for pointing me in the right direction.

    spoke too soon, HALF of it is working, the other is only a "TCollection" instead of a DbExpression now. I'll check it out more

    and yes, using the beta
  • well, many months later i figured out what it was


    i had added unneeded namespaces that was confusing intellisense

    i took out

    System.Data.Entity.Core
    System.Data.Entity.Core.Common
    System.Data.Entity.Core.Common.CommandTrees
    System.Data.Entity.Core.Common.CommandTrees.ExpressionBuilder
    System.Data.Entity.Core.Common.CommandTrees.ExpressionBuilder.Spatial
    System.Data.Entity.Core.Common.EntitySql
    System.Data.Entity.Core.EntityClient
    System.Data.Entity.Core.Mapping
    System.Data.Entity.Core.Metadata.Edm
    System.Data.Entity.Core.Objects
    System.Data.Entity.Core.Objects.DataClasses


    and selectmany worked fine
Sign In or Register to comment.