The Results window gets cluttered as I debug my code, especially with the Dump results.

Please provide a menu option to clear out the Results pane.

For LINQPad controls : add a ScrollIntoView() function. This would cause the query window to scroll to wherever it landed on the Dump() output.

I am a huge fan of the new ContinueButton().Dump().Wait approach found online

however when using it for something that enumerates a large list, it would be really nice to be able to attach a keyboard event to it in the output window so i don't necessarily have to click to trigger it.

As it stands you need to define a style using Util.HtmlHead.AddStyles
I would love to be able to say:
new Button("Do Something", ...) { CssStyle = "margin-left: 5px;" };

When LINQPad hits a hard limit on output size, the query continues
execution but no longer renders .Dump() output.
The idea is to pause execution & add a 'clear output window' hyperlink to the "Limit of query" message to allow script to continue.

This could be an option in case people dont want this behavior.

This would allow to start LinqPAD in a specific working directory and allow a script to do some work in there.

In most of the projects that I work on, we don't usually set DbSet<T> properties inside the DbContext and we rely on the IEntityTypeConfiguration<T> to set the names of the tables.

It would be a great idea to support dynamic dbsets without the need for setting the dbset for each entity that I need to use in LINQPad

LINQPad only supports "kj" for now..

If using #load on a .NET 6 C# file that used implicit usings, LINQPad will complain when using anything from the implicit namespaces, such as saying that the type Action<> could not be found when System is implicit. It would be nice if LINQPad could handle implicit usings so if I #load such a file, it should function properly.

Can we have an option to keep the dialog "Navigate to query" open.
It usally takes a few tries before I find the query I am looking for and it would be great if I could tick a box to keep it open after I dbl clicked to see the query

If I want cross-execution (being able to F5, F5, F5) cache certain fetched web pages (only if they actually return a 200ish result). I can't make use of the existing very helpful cache method options.
I don't want a failed attempt to be cached, and I want to be able to cache all
successes.

I'd like it if we could have the following signature off the existing Util class T CacheIf<T>(string key, Func<T> f, Func<T,bool> predicate, byref<bool> fromCache) also very useful IsCached(string key).

A work around would be to litter the code with throws and try/catch.

Minor suggestions or options,
1: restart button (Execute, Break, Cancel, Restart) & customizable shortcut for it.
2: results pane growing results backwards, the newest line(s) on top of the pane, this would help debugging and testing hardware (IoT:s) a lot.
I know, there is auto scroll option, but LIOT (last-in-on-top) would be nice.

In LPRun.exe we have the ability to only compile the script with the
-compileonly switch.
It would be nice if we had the same in the GUI IDE.

Thanks in advance.

Hi
I found an strange Exception eg. Bug in LinqPad.
Following Code works:
´´´
var e = foo();
e.Dump();
string foo() { return ""; }
´´´

But if I add any Reference on *.dll over F4, "Additional References" and "Add/Browse"

I get on .Dump() following Exception:
"The type initializer for 'DumpExtensions' threw an exception."
inner Exception: The invoked member is not supported in a dynamic assembly.

This stops the practical using of Dump() in my Code.

The VsVim Visual Studio extension honours the "set relativenumber" instruction in _vimrc. It causes the current line to show the absolute line number, and all other lines are numbered relative to it.

3
2
1
584 // TODO: Removing this line breaks the app. We don't know why...
1
2
3

Something similar in LINQPad would be a lovely tweak!