Download LINQPad v7.3.9 (Any CPU) Premium (x64)

LINQPad v7.3.9 (Any CPU) Premium (x64)

LINQPad v7.3.9 (Any CPU) Premium (x64)
LINQPad v7.3.9 (Any CPU) Premium (x64)

LINQPad is not just for LINQ queries, but any C#/F#/VB expression, statement block or program. Put an end to those hundreds of Visual Studio Console projects cluttering your source folder and join the revolution of LINQPad scripters and incremental developers. Reference your own assemblies and NuGet packages. Prototype your ideas in LINQPad and then paste working code into Visual Studio. Or call your scripts directly from the command-line. Experience LINQPads rich output formatting, optional debugger and autocompletion, and the magic of dynamic development and instant feedback!

The .NET Programmers Playground
Instantly test any C#/F#/VB snippet or program
Query databases in LINQ (or SQL) SQL/CE/Azure, Oracle, SQLite & MySQL
Enjoy rich output formatting, optional autocompletion and integrated debugging
Script and automate in your favorite .NET language
Super lightweight single 15MB executable!
Standard edition free, with no expiry

LINQPad: The Ultimate .NET Scratchpad
LINQPad can run not only LINQ queries, but any C#/F#/VB expression, statement or program.
For instance, have you ever needed to test a DateTime format string? In LINQPad, just enter the expression and hit F5:

With LINQPad's instant edit/run cycle and optional full autocompletion, you'll have code snippets fully tweaked in less time than it takes to bring up Visual Studio's Add Reference dialog!

What about testing a regular expression? You'll start using Regex a lot more once you have LINQPad:

Notice how LINQPad nicely formats the Match object. Complex object graphs are much more readable in LINQPad's output window.

To run a series of statements, just change the "Language" combo to Statements (or hit Ctrl+2):

Again, you can keep tweaking your code until it does what you want, then paste working code into Visual Studio.

You can even run a full program with additional methods: just change the Language to Program, and LINQPad will wrap your code in a Main method so you can write additional methods and classes.

Need to reference custom assemblies or NuGet references? No problem: just hit F4 for the Add Reference dialog.

Additional benefits:

LINQPad reports the execution time in the status bar, so you won't have to manually create a Stopwatch class for performance testing.
Want to test a variation of your snippet? Ctrl+Shift+C instantly clones your snippet so you can run another version side-by-side.
You can return to saved queries in single click, thanks to the My Queries treeview. Use LINQPad as a scripting tool!
You can call Dump on any WPF or Windows Forms control and LINQPad will render it. This is a great way to write custom visualizers.
In the My Queries treeview, you'll see a query called My Extensions. Here's where you can write methods and classes that will be available to all queries.

LINQPad 7.1

New Features
LINQPad 7 now supports F# 6.
Connections configured for .NET 6.0 now always use the requested framework if available, regardless of your default framework choice. This avoids compilation errors that might otherwise result.
Util.Dif's text diffing is now more aggressive in looking for differences when comparing single-line strings.
The MySQL and PostgreSQL drivers have been updated to .NET 6.0.
When dumping structs, LINQPad now descends into fixed-length buffers.

The CMD symbol now works correctly when running scripts with LPRun7.
Queries with the "Reference LINQ-to-SQL" checkbox enabled should now work with the right assemblies.
When dumping a DataTable in DataGrid mode, an icon now appears when a RowError property is set.
A startup error that was affecting some users has been fixed.
A number of edge-cases that could cause the auto-generated LINQ-to-SQL data context not to compile have been fixed.
A package restoration error that sometimes appeared when enabling spatial types in the EF Core dialog has been fixed.
If .NET 6 hasn't been installed, EF Core connections will use EF Core 5 instead of EF Core 6.
An intermittent error that sometimes appeared when restoring NuGet packages from a local source has been fixed.

Only for V.I.P
Warning! You are not allowed to view this text.
  • 21