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! :)

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.

Util.Run with dbcontext as parameter to run scripts against different context

It would be nice if hovering over the menu titles caused the menus to dropdown and show the items, rather than requiring a click action on the menu titles.

I often have multiple LINQPad windows open under different credentials, required for operations against remote servers, but I loose track of which is which. I'd be handy for me to show the username in the title bar (perhaps only if impersonating via RUNAS)

When typing out the method call I would like to be able to see the different overload methods and their XML summary. Currently we are able to see the overload's for the call and what the summary of the parameters of that call but not the summary of the actual overload.

After I have finished the call I am able to hover over the call and see but it would be nice to see the summary while I type.

Intellisense does not working on big queries. I've an query with about 6.000 lines of code and intellisense does not working inside. On other (smaller) queries intellisense works fine. Using LP v5-03-03 beta Any CPU.

Provide support for Linq to Collections, Linq to DataSet, Linq to XSD and Linq to Objects.

I found LINQPad can also support SQL command query and this does make helps sometimes. However, the left-up view can only show the entity model, it's will be more helpful if this view can also show the physical data model like many other SQL tools show. By referring this physical data model we can make correct SQL commands more easily.