Skip to content

LINQPad Feature Suggestions

More than 100 LINQPad features are a direct result of customer feedback! This is the official forum for posting and voting on ideas – we want to hear from you!

LINQPad Feature Suggestions

Categories

I suggest you ...

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

2 results found

  1. Add the Expression Tree Visualizer

    The Expression Tree Visualizer is a fantastic tool to shed some light on exactly what happens when an expression tree is invoked. It's especially useful when building your own from scratch, and some visibility on how LINQ does it would be a real bonus!

    50 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…)
    2 comments  ·  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
    under review  ·  AdminJoe Albahari (LINQPad) (CEO / Founder, LINQPad) responded

    Are you aware that you can call .Dump() on an expression? The output is not exactly the same as the Expression Tree Visualizer, but it conveys much of the same information. Is there anything missing from what you see that you’d like added? Or anything that you’d like changed?

  2. Allow definition of symbol for configured database connections

    It would be useful if I could define a symbol in a database connection.

    I would then expect that I'd be able to define either conditional extension methods in the "My Extensions.linq" file, which would then be conditionally built based on the database I'm connecting to (and thus could potentially reference/use the types from that connection).

    An alternative/secondary thought - is a way of linking/specify a base query (basically just a way of ensuring @load is done) for any a db. That way any time I'd start a new linq query, it would either automatically add the @load line -…

    3 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…)
    0 comments  ·  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
  • Don't see your idea?