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

(thinking…)

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.

5 results found

  1. Allow conversion of SQL to Linq (where possible)

    It would be great if I could paste in an existing SQL query and convert it to LINQ. This capability exists in other tools, but I would prefer to use LINQPad for everything.

    116 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…)
    10 comments  ·  Admin →
    declined  ·  AdminJoe Albahari (LINQPad) (CEO / Founder, LINQPad) responded

    In general, LINQ is a higher-level (more abstract) querying language than SQL and this creates some major scope for translation loss in a SQL→LINQ direction. For one, LINQ emits shaped results whereas SQL emits flat result sets. The upshot is that an automatic translation from SQL to LINQ will often have to perform more of a transliteration than translation – and generate examples of how NOT to write LINQ queries. For this reason, I’m loathed to implement such a feature. It would be rather like writing a tool to convert VB6 to C# 4, and then using the output to “learn” C# 4.

    To use LINQ properly, you must learn to translate your requirements DIRECTLY into LINQ. If you think first in SQL and then translate to LINQ, you’ll get the worst of both worlds!

  2. SQL 2008 support

    8 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 →

  3. Ctrl + U to set focus on database selection combo

    As per SSMS functionality.

    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  ·  Admin →

  4. an option to turn off autocompletion

    There are some very complex queries where the autocompletion works extremely slow and thus doesn't let edit the query (it stuck every few seconds).
    An option to turn-off the autocompletion should be introduced for these cases.

    Thanks

    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…)
    2 comments  ·  Admin →

  5. Can Dump() work on "dynamic" objects?

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