I use LINQPad to work with libraries based on previous versions of .NET, and it would be helpful to be able to edit the App.config like I could in LINQPad 5.

I love the new feature where you can load other linqpad files with the #load directive this makes my linqpad file way more reusable and modular, however...

When I have 3 files where file 1 includes file 2 and file 2 includes file 3 then file 1 also have to include file 3 even when not using any functionality from file 3 in file 1.

It would be great if file 1 does not have to include file 3.

Put resource dll's into subdirectories, similar to where they were originally: e.g., .\ja-JP\x.resources.dll; .zh-CHS\x.resources.dll, etc.

I made a script to modify a registry key, and I realized I needed to run it as an admin for the script to work. I needed to save the script first, so I could close LinqPad, and reopen it as an admin. Some way to elevate the current query, or reopen LinqPad as admin without needing to save would be cool.

I don't often want or need to save the output from a LinqPad script, but when I do I almost invariably need to end up with a PDF that will be sent to someone else. The current export options (Excel, Word, HTML) get the job done but require an additional step. It would be really nice if LinqPad could export directly to PDF

Possibility to add custom aggregates like sum, average over custom types for the Dump method.

Currently you get a sum/average underneath columns containing int's etc. (except if they are formatted through ToDump).

It would be nice to do something similar as ToDump for custom types, and or types like TimeSpans, Dates, etc.

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

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.

It would be useful to have a tab before "My queries" with the preferred queries to get a link to start them quickly, also visible in the search query, to simply find the correct script.

We have thousands of queries in 8 years that we use LINQPad.

I just upgraded to LINQPad 6, and I cannot see the views from my database, only the tables.
I am connecting to a MySQL database.
I was able to see the views in LINQPad 5 just before the upgrade.
Thanks.

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 dumping objects it would be nice to see which properties are marked as Obsolete by striking through them.

Display a timestamp for each SQL statement on the SQL tab so that the user can see when and how long between each command was executed.

Add a tools menu or function to send the current file or query including row and column location of the cursor to an editor.

Some Windows updates wipe out a recovery file.

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.

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.

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

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

It would be great if there was an option for each NuGet package in the LinqPad NuGet manager that allows you to set a package to auto update when a new version of the package is released.

We connect LinqPad to internal NuGet packages and the consumers of these packages should always be up to date with the latest versions of our internal packages.

When right-clicking on a query, add an option to close queries to the right of currently selected query. Dialog-wise when handling unsaved queries is at your discretion, but I can see something as follows:
-If there's no unsaved queries, don't prompt asking to save.
-If there's one unsaved query, do a prompt asking to "Save Query X?".
-If there are multiple unsaved queries, do a prompt asking to "Close all unsaved queries to the right of [currently selected query name]