Show IL Code Description not just as Tooltip but optionally behind the IL code in each line

allow for relative reference to a config file.... something like.....

[QueryPath]\app.config

and/or

currently if no path info is supplied (just file name) the LP app assumes the file location to be the folder of LP.... maybe look in query path folder first?

This would allow for more portability of scripts... might be able to just package up the folder... relative references will allow things to run on the other end without having to make path tweaks.

Since a SelectBox can have multiple selections, it would be useful to have a constructor overload which takes in a List<int> to specify multiple SelectedIndexes.

For example, trying to use the following method defined in a .NET Standard assembly:

public static (object o, string objectName, string category)[] GetTestObjects() => ...

Updating content of a DumpContainer doesn't trigger an auto scroll.

Run this code in c# statements or c# program mode:

Util.AutoScrollResults = true;
var container = new DumpContainer().Dump();
var builder = new StringBuilder();

while (true)
{
container.Content = builder
.AppendLine($"{DateTime.Now:fff}")
.ToString();
Thread.Sleep(150);
}

Add editor command to insert a new GUID into the query text.
The current workaround requires opening another tab and running Guid.NewGuid() command there, then copy-pasting back to original query.

I thought earlier version of LinqPad allowed for setting the default font size, and has removed it in light of allowing use to zoom in. While it would be nice to allow both options actually, the default font size, and/or the default zoom. Also it seem the result in the Dump() don't pick up the font size in the query window. Might assert if one need to zoom the font to see the query, 99.999+% (or more) we will need to zoom the results from the dump as well? :)

When writing long statements (Specially Linq fluent statements) we tend to break them into multiple lines. However the first line break in LP starts at the same position as the first line and we always need to tab (or spaces) so that lines from 2nd onward appears nicely.

Since linqpad 6 has been migrated to dotnet core, would it be possibile to provide an Linux build?

Dbus is a cross platform desktop integration bus, and has properties similar to Activex and Com. This would be to allow LINQpadto glue windows applications (when run in wine) to a Linux Desktop, or Mono application with Dbus support on a mac.

The indent command shouldn't indent the #region/#endregion statements just like it doesn't indent #if/#endif.

I am trying to creat connection but i am unable to connect.
Let us know what exactly the parameter here for http://{MachineFQDN_OR_MachineIP}/ Citrix/Monitor/OData/v1/Data
MachineFQDN_OR_MachineIP}/ --- Database server on which monitoring database is residing or Desktop director server name.
Citrix---?????
Monitor ---- is the instanse name

I often connect to databases individually on a Production server because of the way our security works. These connections are temporary and transient for security reasons.
Rather than marking a connection as Production each time it would be helpful if I could configure the server as a Production server and then each time I connect to an individual database it is automatically marked as Production.
Thanks!

When collection contains more items than the limit in the rich text mode the header says "First n rows". If the object implements ICollection or IReadOnlyCollection it would be nice to show "First n rows of {dumpedObject.Count}"

The tool tips for the function signatures, such as Select, Join, GroupBy, take up screen space and obscures typing. Unlike other editors, the tool tips do not move properly when the cursor moves to new locations in the editor. These tool tips are obtrusive and require hitting escape key constantly so I can see what I am typing. Should be able to disable in Preferences.

Is it possible to use linqpad 5 with odata driver using metadata stored on a local file ?

I would like to be able to debug inspect each step of linq queries.