I suggest you ...

Don't automatically populate the connection when creating a new query

Sometimes when I start up a new query, I type a single C# expression like "Environment.OSVersion" and then hit run. It doesn't execute instantly and I look at the status bar and see "Fetching Schema...". Then I see that LINQPad automatically assumed that I was going to use the connection I used last time I wrote a query and added it for me. Although this may be useful for someone who uses LINQPad exclusively for querying a single database, this is annoying for others who use it as a C# scratchpad or frequently query different data sources.

3 votes
Vote
Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
You have left! (?) (thinking…)
Joe Skeen shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

0 comments

Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
Submitting...

Feedback and Knowledge Base