linq2db.LINQPad 6.6.0

Prefix Reserved
dotnet add package linq2db.LINQPad --version 6.6.0
                    
NuGet\Install-Package linq2db.LINQPad -Version 6.6.0
                    
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="linq2db.LINQPad" Version="6.6.0" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="linq2db.LINQPad" Version="6.6.0" />
                    
Directory.Packages.props
<PackageReference Include="linq2db.LINQPad" />
                    
Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.
paket add linq2db.LINQPad --version 6.6.0
                    
#r "nuget: linq2db.LINQPad, 6.6.0"
                    
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
#:package linq2db.LINQPad@6.6.0
                    
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.
#addin nuget:?package=linq2db.LINQPad&version=6.6.0
                    
Install as a Cake Addin
#tool nuget:?package=linq2db.LINQPad&version=6.6.0
                    
Install as a Cake Tool

LINQ to DB LINQPad Driver

This nuget package is a driver for LINQPad 8 and newer, on Windows and macOS (LINQPad 9 recommended), with queries running on .NET 10 or newer. LINQPad 5 is supported by the .lpx plugin published with each release. Support for older LINQPad versions is available in older driver versions.

Following databases supported:

  • ClickHouse: using Binary, HTTP and MySQL interfaces
  • DB2 (LUW, z/OS, iSeries): 64-bit LINQPad only — the LINQPad 5 .lpx also supports 32-bit
  • DB2 iSeries: check release notes to see which version supports this database
  • DuckDB
  • Firebird
  • Informix: 64-bit LINQPad only — the LINQPad 5 .lpx also supports 32-bit
  • Microsoft Access: OLE DB and ODBC drivers (Windows only); managed LibRed engine on every OS, on the prerelease LibRed.Ado package (not in the LINQPad 5 .lpx)
  • Microsoft SQL Server 2005+ (including Microsoft SQL Azure)
  • Microsoft SQL Server Compact (SQL CE) (Windows only)
  • MariaDB
  • MySql
  • Oracle
  • PostgreSQL
  • SAP HANA: both Native and ODBC providers (ODBC needs the SAP HANA ODBC driver installed; with the LINQPad 5 .lpx, Native needs the SAP HANA client installed; not available in an ARM64 LINQPad on Windows, as SAP ships no Windows ARM64 client)
  • SAP/Sybase ASE
  • SQLite
  • YDB

Installation

  • Click "Add connection" in LINQPad.
  • In the "Choose Data Context" dialog, press the "View more drivers..." button.
  • In the "LINQPad NuGet Manager" dialog, find LINQ To DB driver in list of drivers and click the "Install" button.
  • Close "LINQPad NuGet Manager" dialog
  • In the "Choose Data Context" dialog, select the "LINQ to DB" driver and click the "Next" button.
  • In the "LINQ to DB connection" dialog, supply your connection information.
  • You're done.

Database clients

This nuget package doesn't bundle database client libraries. LINQPad downloads the client of a database when a connection to it is first used, so using a database type for the first time needs an internet connection. A static data context selects its provider itself, so the driver cannot detect which client it needs: such a connection downloads all of them unless you pick its database in the "Database" field of the connection dialog. Note that a context assembly which references a client library must be able to load it from its own folder, because the connection dialog inspects that assembly before any client has been downloaded. A dotnet publish folder has the client next to the assembly, and so does the build output of an application referencing it; the build output of a class library does not, because the .NET SDK doesn't copy NuGet dependencies there unless the project sets CopyLocalLockFileAssemblies to true. If the client cannot be loaded, the context classes that don't need it are still listed and the rest is reported in the log; the "Context" field is editable so the class name can be typed in either case.

The LINQPad 5 .lpx plugin is unaffected by any of this — it ships every client in the bundle.

Licensing

The MIT license this package declares covers LINQ to DB's own code. The nuget package itself bundles no third-party binary — the database clients above arrive as ordinary NuGet dependencies under their own licenses.

The LINQPad 5 .lpx plugin is different: it bundles every client, so it redistributes third-party software directly. Its THIRD-PARTY-NOTICES.txt, inside the plugin archive, lists every bundled component and reproduces its terms.

macOS

Databases that need Windows-only components — Microsoft Access and SQL Server Compact — are not offered on macOS. Everything else uses the macOS build of its client, including IBM DB2 and Informix. The SAP HANA native provider uses the macOS build of its client too, but is untested on macOS. SQL Server spatial values (geometry, geography, hierarchyid) are handled by the managed dotMorten.Microsoft.SqlServer.Types implementation, as Microsoft's package ships its native spatial library for Windows only.

Troubleshooting

Driver errors are written to linq2db.LINQPad.log, in the Logs.LINQPad<version> folder of LINQPad's application data directory:

  • Windows: %localappdata%\LINQPad
  • macOS: ~/Library/Application Support/LINQPad

On macOS, errors raised outside of the connection dialog go to that log only, without a message box: LINQPad renders a driver's dialogs through Avalonia XPF there, and XPF is available to a driver just while its own dialog is open, so anything reported from elsewhere has nowhere to draw. On Windows they are shown in a message box as well.

Failures the driver recovers from go to the log on either system, without a message box. Reading the age of a connection's schema is one: LINQPad asks for it before it has downloaded that connection's database client, so it cannot be answered yet, and the schema is built and queried normally straight afterwards.

Product Compatible and additional computed target framework versions.
.NET net10.0 is compatible.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
6.6.0 77 11/18/2026
6.5.1 251 10/23/2026
6.5.0 380 9/11/2026
6.4.0 614 8/7/2026
6.3.0 726 5/17/2026
6.2.1 685 3/17/2026
6.2.0 241 3/12/2026
6.1.0 1,175 12/15/2025
6.0.0 394 12/5/2025
6.0.0-preview.3 286 2/2/2025
5.4.2 5,793 10/11/2024
5.4.1 1,123 9/1/2024
5.2.2 3,222 3/10/2024
5.1.0 5,119 6/9/2023
5.0.0 1,465 4/22/2023
4.2.0 4,979 9/6/2022
4.1.1 2,324 7/2/2022
4.1.0 848 6/27/2022
Loading failed