Skip to content
← Customer Feedback for LINQPad

Settings and activity

3 results found

  1. Dump of enumeration of inherited objects should display actual classes

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  LINQPad Feature Suggestions  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    An error occurred while saving the comment
    David Mårtensson commented  · 

    An example.
    An enumeration of Nodes where each node can be of text or number would be listed as "Enumerable<Node>" and the lines show no classname.

    David Mårtensson shared this idea  · 

  2. Show correct line-numbers in stack-traces

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  LINQPad Feature Suggestions  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    David Mårtensson supported this idea  · 

  3. Define query templates

    92 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    9 comments  ·  LINQPad Feature Suggestions  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    An error occurred while saving the comment
    David Mårtensson commented  · 

    I was just about to suggest something like this but more like a Context that I could choose for a query.

    By selecting a context I get all the above but with contexts I could also switch context.
    Like testing the same query towards different builds of the same product.

    In my case I have methods that are named the same in two different projects and if I include both they become ambiguous.

    But since changing references and namespaces is cumbersome I have all included and remove the unnecessary once, but this also is a bit irritating to have to do.

    Please implement something like this :D

    David Mårtensson supported this idea  ·