title pretty much explains it, but in SQL Management Studio there is an option to filter the listed tables you see in the left handed tree view by applying a filter to match with

Would be great if LINQPad supported WIndows 10 ARM64 build.
As of Feb 2020 .NET 5 preview doesn't support Windows Forms and WPF and will be released in Nov 2020 and .NET 3.1 doesn't support ARM64 Windows devices at this time.
Thanks

The EF Core DbContext that supports the DbContextOptions<TContext> does not support any other configuration options -- just the connection string. I really need it to allow Lazy Loading supports and Detailed Errors.

THANK YOU.

This should be available in this software. As someone that has years of experience in SQL, I find LINQ syntax to be appalling and extremely confusing. I bought the professional version in hopes that this software implemented this feature, it does not, and yes I read the previous request and your reply to the user about VB6 to C# 4 comparison but highly disagree with your decision.

For example JSON/XML/CSV/Excel data used for testing out a snippet or library.
Just for the overall convenience... and when you get back 6 months later and look for the input data!

I tried to use System.ServiceModel.Primitives NuGet package and specifically the SynchronizedCollection<T>. However after installing the package I'm getting the following error when declaring variable of type SynchronizedCollection<string>:

CS0433 The type 'SynchronizedCollection<T>' exists in both 'System.Private.ServiceModel, Version=4.7.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' and 'System.ServiceModel.Primitives, Version=4.7.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'

The same works fine in Visual Studio (.NET Core Console App project).

LINQPad 6.8.1.

If I point LinqPad6 to a new My Queries (and Snippets and Plugins) folders, LinqPad5 is updated to the new folders as well. But I have years worth of queries with .Net Framework Dependencies and would like a clean My Queries structure for LinqPad6 with only .Net Core dependencies.

the tooltip is very (very!) frequently in the way of typing in code.

first of all, the tooltip should NEVER obscure the cursor (it should just move out of the way), and, to ensure it doesn't have to move out of the way too often, make it appear near-ish (not near) the cursor. Like a couple of lines below the current position of the cursor, so you at least have a few lines of respite, before having to press esc to get rid of that annoying tooltip

With the new Uncapsulate method in the beta, I tried dumping the internals of an unfinished task, because I'm trying to learn more about some internals of the tasks and the task scheduler.

However, it dumps as "awaiting...".

Could there be a way to force a dump now, even though the task hasn't finished? In my case, it was a task that will never finish because I created it expressly to know what the internals look like before it has completed.

So this:

new Task(() => { }).Uncapsulate().Dump();

will just show "awaiting...".

I use LINQPad a lot with a lot of proprietary company code and connections. I love the instant share feature, but it would be awesome if we could set a custom share location that wasn't public, for example a custom path to a file share. Thanks!

I haven't been able to find a setting to turn this off:
https://imgur.com/a/ESbuHpK

string str = "ABC";

string Duplicate()
{
return str + str; // str is not recognized by the debugger
}

Duplicate();

Add support for c# local ref vars in the watch window.

For example given code like below
void Main()
{
var sx = new st { i = 1 };
ref var rx = ref sx;
rx.i.Dump();
}
struct st { public int i; }

Add support for the expression rx.i in the watch window

Dark mode doesn't change the color of the title bar or the buttons and controls on the toolbar.

Also, dark mode feels extremely clunky as most parts of the app start as white and change to dark several seconds later. It's not unusable since it does go dark eventually but if that could be fixed, it would be a considerably less jarring user experience.

When a script completes with warnings... provide a method for jumping to the line in the script that surfaces the warning. Perhaps clicking on the warning message (jump to first warning line)... or at least including the line number(s) of warnings.

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.