Best Of

Thanks - I've managed to repo it on a laptop. It's the Windows listbox itself that's the culprit - it doesn't work well with 14k items. I will release a workaround soon that will more aggressively filter in that scenario, making the delay when typing will much less noticeable.

Check out 7.6.1 - there's now a Video control in LINQPad.Controls.

@Achim there is a batter way to have self-contained dump output, as previously mentioned at https://forum.linqpad.net/discussion/comment/2562#Comment_2562, though I had to make a slight modification.
Put the following code to your "My Extensions":

public static object ToDump(object input)
{
    var image = input as System.Drawing.Image;
    if (image != null)
    {
        using (var ms = new MemoryStream())
        {
            image.Save(ms, ImageFormat.Png);
            return Util.Image("data:image/png;base64," + Convert.ToBase64String(ms.ToArray()));
        }
    }
    return input;
}

Then output chart as bitmap and you will have all resources in the same output:

string[] xSeries = { "John", "Mary", "Sue" };
int[] ySeries = { 100, 120, 140 };
var chart = xSeries.Chart().AddYSeries(ySeries).ToBitmap(500, 300);
Util.ToHtmlString(chart).Dump();

I know this is a very old thread, but I was struggling with these same problems (in V5, V6, V7). After a lot of troubleshooting, I found out that in all of my LP scripts where this slowness/stuttering of intellisense/autocomplete occurred, I imported the Microsoft.Graph namespace, which is huge with a lot of types. After removing the namespace import, and just using the full type paths instead (eg. Microsoft.Graph.GraphServiceClient), the intellisense slowness/stuttering stopped, and everything went to normal again.

Does not work with C# Statements, so change your script to be C# Program.

I know this is an old question, but for anyone else looking for the answer like I was today, I just converted my IDictionary<string, object> to ExpandoObject with the below extension method and it work as expected.

    public static dynamic ToExpando(this IDictionary<string, object?>? dict)
    {
        IDictionary<string, object?> expando = new ExpandoObject();
        if (dict == null)
            return expando;

        foreach (var (key, value) in dict)
        {
            expando[key] = value;
        }

        return expando;
    }

LINQPad creates those classes on the fly via a built-in scaffolder. You can see what it generates by pressing F12 (go to definition) on a database symbol or pressing Alt+Shift+R and then manually navigating in ILSpy.

I'm not sure what you mean by I can de-refer the DbContext reference and use the recordTable object created in LinQPad object explorer

Does that mean you are using the Default Linq to SQL connection? If so then I don't think that will work. You would need to select 'Use a typed data content from your own assembly and point it to your EF dll.

Then add a reference to System.Data.Entity.dll and add the namespace System.Data.Objects.SqlClient

Note, I think this should work, but I can't test this because I don't have a EF6 typed data context dll that I can use and SqlFunctions does not work with EF Core.

.NET 7 added support for printing JIT disasm on-the-fly using the DOTNET_JitDisasm environment. Users can set DOTNET_JitDisasm to a specific method or use * to match all methods, and then the coreclr will print the JIT disasm (it's more detailed than using clrmd) to stdout while code is running.

I hope that LinqPad can add support for setting DOTNET_JitDisasm manually.

Also, LinqPad can also add support for tiered compilation, OSR and PGO, which is controlled by environment variable DOTNET_TieredCompilation, DOTNET_TC_OnStackReplacement and DOTNET_TieredPgo, respectively.

This should now be fixed in 7.5.7. Let me know if it's still an issue.