LINQPad Premium 9.5.10 x64

General
LINQPad now supports .NET 9 RTM.
LINQPad's samples now include 'What's new for C# 13.'
LINQPad can now execute .cs files that define a file-scoped namespace.
Fixes
A regression in the how the debugger's stack trace handles recursive methods has been fixed.
The HTML Image control in LINQPad.Controls is now more flexible in how it handles attributes and styles when a Util.ScaleMode is specified.
A bug in LINQPad's EF Core driver that prevented MySQL version 3.x from working has been fixed.
The LINQ-to-SQL driver now correctly lists stored procedures that use table types.

Security Updates
LINQPad now uses Azure.Identity 1.11.4, in response to CVE-2024-35255.
New Features - Dump
Util.Dif can now detect inserted and removed items in lists of complex objects.
There's a new DumpOptions class that can be used for specifying parameters when calling Dump. This supports additional options such as MaxRows (to increase or decrease the row limit in HTML mode from the default of 1000), and FormatStrings, which allows you to specify format strings for numeric and date/time types on a per-Dump basis. (This overrides any global defaults specified in Edit | Preferences.)

You can also set defaults for a query via the static DumpOptions.Default property (or Util.DumpDefaults):
DumpOptions.Default.MaxRows = 20000;
DumpOptions.Default.FormatStrings.DateTime = "yyyy-MM-dd";
DumpOptions.Default.FormatStrings.IntegralNumber =
DumpFormatStrings.Constants.IntegralNumberWithGroupSeparator;

Enumerable.Range (0, 20000).Select (days => new { days, Date = DateTime.Now.AddDays (days) }).Dump();
You can now force the expansion of objects that implement IFormattable (such as DateTime), either by specifying a depth when calling Dump, or with DumpOptions.ForceExpansion.
ValueTask is now treated like Task when dumped.
There's a new DumpAsync method for IAsyncEnumerables. This behaves just like Dump except that it returns an awaitable Task that completes when the Dump has completed. This allows you to ensure that execution does not proceed until the sequence has been fully awaited.
Exceptions stack traces now include hyperlinks when dumped.
New Features - EF Core Support
Many-to-many relationships in custom EFCore models are now shown in the Schema Explorer.
Populated EFCore associations are now rendered automatically when dumped.
The dialog for custom EF Core connections now lets you pick DbContext types that are marked as internal, if the defining assembly includes the [InternalsVisibleTo("LINQPadQuery")] attribute.
When defining custom DbContext classes for use with LINQPad, you can now include additional optional parameters in the constructor that accepts a DbContextOptions parameter. For example:
public class SchoolContext : DbContext
{
public SchoolContext(DbContextOptions<SchoolContext> options, string extraData = null)
: base(options)
{
...
}
...
LINQPad will pass in the default value for any optional parameters (null in this example).
New Features - General
You can now Ctrl+Click on symbols to navigate to their definition (or reflect in ILSpy).
When LINQPad displays parameter lists for overloaded methods, it now does a better job of jumping to an overload compatible with what's been typed so far.
Util.Run now lets you specify file paths relative to where the calling query was saved (matching the behavior of #load). As before, file paths can also be relative to Environment.CurrentDirectory or the My Queries folder. You can also now omit the .linq file extension.
LPRun.exe can now resolve paths relative to the My Queries folder, and lets you omit the .linq file extension.
LINQPad's editor now supports .tsv files (tab-separated-values).
The contents of Span and Memory types now show in the debugger.
Fixes
A thread-safety issue that could cause duplicate headings when dumping from multiple threads concurrently has been fixed.
A bug in Util.Cache's serializer that could cause it to ignore private fields has been fixed.
LINQPad's now take steps to ensure that the resolution of a .NET assembly overridden by a newer version from NuGet is not upset by the presence of a downstream .NET assembly that's not overridden.
Tables named 'file' and 'system' no longer cause an error with the LINQ-to-SQL or EF Core drivers, regardless of property capitalization settings.
LINQPad now correctly processes databases with non-unique foreign key constraint names, as long as each name is unique per schema.

Security Updates
LINQPad's EF Core driver now forces the use of Azure.Identity 1.11.0 when the SQL Server provider is selected, to work around CVE-2024-29992.
New Features
LINQPad 8 now supports the .NET 9 preview and the EF Core 9 preview.
NuGet packages that contain only satellite assemblies are now supported in LINQPad.
ILSpy has been updated to version 8.2.
Dump in Data Grid mode now supports the include and exclude options to include or exclude specific properties or fields.
When inside a generic method or class, the debugger's Threads and Call Stack windows now show the type parameters in the code location.
Util.ToHtmlString and Util.CreateXhtmlWriter now emit HTML that's more consistent with what's rendered in the results window.
LINQPad now automatically applies XML comments on interface members to their implementations, if no other comment is available.
The maximum HTML content length for the results window has been increased.
Fixes
An intermittent problem that could cause duplication when appending data to a DumpContainer has been fixed.
A scenario in which the asynchronous use of Util.Cache could hang instead of throwing an exception has been fixed.
You can now reliably copy and paste cells from LINQPad-generated Excel spreadsheets without error.
TabControl keyboard navigation shortcuts now work correctly in the Query Properties dialog.
Progress bars generated with Util.ProgressBar are now visible immediately after being dumped.
A parsing bug that could prevent the entry of negative numbers when editing tables in Data Grid mode has been fixed.
When an subclass hides a base class member with C#'s new keyword, LINQPad's Dump engine now ensures that the subclass's member takes priority.