Display the cursor line and column in window footer like VS, PowerShell ISE, SQL Developer, Notepad++ and other applications

It should be useful to rename the method to Util.SaveData and add a description to better explain what is the saved value, not only the key.

And add an overload to save data linked with a LINQPad user to allow to have different values for the same key to export and import the passwords to other machines across the team.

I've created a script to export/import the password using an encrypted .ZIP file.

Thank you!

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.

When I have a "Customers" table, please support having "Customer" entities.

At the moment, I have the "Customers"-table in the tree view with a "Customers" entity data type, which is bad.

When you use Open in Excel on a grid, the Excel (html) file that is opened is named after the query name, but should be named after the Grid title from the Dump command that created the Grid, if one exists.

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!

With SQL Azure in general and now specifically with the new serverless option it would be great to be able to enable the various ADO.NET and EF Core resiliency options so that you do not get a timeout on startup or when there is a transient failure. Both are just settings for number of times to retry, the retry interval, etc.

For EF Core with SQL you can use something like
optionsBuilder.UseSqlServer(cstr,
sqlServerOptionsAction: sqlOptions =>
{
sqlOptions.EnableRetryOnFailure(
maxRetryCount: 18,
maxRetryDelay: TimeSpan.FromSeconds(5),
errorNumbersToAdd: null);
})

In ADO.NET you can do it in the connection string parameters

ConnectRetryCount=18;ConnectRetryInterval=5;Timeout=90

Thank you

There are a few assemblies I often use in LinqPad queries, that are not in the GAC or on Nuget. Every time, I have to browse to their location to find them (e.g. Windows.winmd to use WinRT APIs). It would be nice if there was a "recently used" list in the "Additional references" tab

Line numbers are present in a beta release , but only for new Query windows and not when viewing/editing Stored Procs in a DB.

It would be nice if we could be able to turn off the Dump of the Unhandeled exceptions, or Change the Default Handler from LINQPad on the 'AppDomain.CurrentDomain.UnhandledException'.

I have not found any way of turning this off without actually using reflection to fetch, and de-register the default, and then re-register my own implementation (it works, but it's buggy).

Currently in the beta charting works really nice, except it is not possible to add an extra XY set, only a Y set can be added using .AddYSeries.

Add optional parameter to Util.Cmd that will accept a parameter so alternate success exit codes can be defined. Currently only 0 is acceptable as a success, but some apps use alternate exit codes.

I'm guessing this would increase speed a lot?

If i work o X DB i have lightred, but i i work on Y DB i work on limegreen editor

https://gist.github.com/nielsbosma/d5425ca23df3f3d6ff20273b7a5efd54