So it is easier to identify. All named "Query 1", "Query 2" doesn't tell much.

make it compatible with UWP

Recently LinQPad seems to have become rather niche, I don't really understand what the new features do or what they are for. For example this nuGet, I've no idea what or why I'd be interested in. I'd vote for a complete documentation similar to the c# in a nutshell series on each feature of LinQPad hi-lighting premium features where appropriate.

The arrow pointing to a currently executing line in the code editor is very helpful as a quick-and-dirty debugging/profiling tool. However, when working with code that is several pages long, the arrow often disappears from view and can be hard to find. An option to always keep the currently executing line visible in the code editor would be really helpful.

A function that autoscripts the data of particular (selected) table(s) into a SQL formatting. It would help me to completely get SQL Enterprise Mngr out... Now I do this via "select database", Tasks, Generate Scripts, Select Advanced button and change the types of data to script to: Schema and Data.

In the Add Connection dialog is a 'Delete Driver' feature, I sugges you add a 'Refresh Driver' to that simply deletes the driver and reloads it again from the same place.

Please make it easy to find and copy the existing activation code from within Linqpad itself. I was going to examine upgrading to version 6 today but can't as I don't have this code to hand. And I couldn't locate it in Linqpad :(

This feature would probably get a few more impulse purchases before Xmas! :)

When querying data with xml, a malformed xml should not stop the querying of other rows. Linqpad should show where the malformed xml is and get the other columns.

I usualy work by batches... at one client I use thoses queries, while at this other one, I use a different set...

And I have like 10-20 queries open, in a specific work context...

Context switching is a bit of a nightmare....

If only I had a button to save not the files themselves, but the specific work context, I could just reopen a previous context and off I'm gone...

VIM Visual Mode:
Type V and hit three times L.
Linqpad selects only 3 characters, whereas the original vim would select 4.

VIM Search replace:
To replace stuff within the current selection, type in VIM
:s/Pattern/Replace/g

New Shortcuts:
ALT+J / ALT+K navigates to the left / right query tab.

Thanks for this awesome tool!

Since VB is case-insensitive, all its keywords can be lowercase without affecting compilation. In Linqpad4, I use to type all my VB code in lowercase (it's somehow much more readable). Now with LP5, I get code completion and other nice stuff, but all my nice lowercase code gets put back in normal VB style. If it's not too much work, a "Lowercase VB keywords" option would be great.

Drag-n-drop a CSV file to the LINQPad window to silently create an IQueryable object populated with its values and insert a code reference at the cursor point where the drop operation completes.

If I never use a certain language (e.g. C#, F# or Visual Basic) I should be able to set an option that will exclude options based on that language from the language dropdown.

I always rename connections so they have a meaningful names and I also use the create similar connection. Unfortunatly, this feature also copy the name and to figure out which of the two I should rename, having a tool-tip with the connection details would greatly help.

The yellow bar at the top shows the current exception but if you have a very long linqpad script you need to scroll down to see where the error happened. It would be nice to be able to click the yellow bar to jump down to the exception.

It would be nice to have comment slashes (//) prepended to the first non-whitespace character of a line rather than the beginning of the line.

Example

Current functionality - Before using the comment shortcut:
void Main()
{
\s\s\s\sConsole.WriteLine();
}

Current functionality - After using the comment shortcut:
void Main()
{
//\s\s\s\sConsole.WriteLine();
}

Desired functionality - After using the comment shortcut:
void Main()
{
\s\s\s\s//Console.WriteLine();
}

• Sorry for the awkward 'regex'-like values representing a space. This wasn't posting with all the spaces.