Downloads of v 5.46.0:


Last Update:

09 Apr 2022

Package Maintainer(s):

Software Author(s):

  • Joseph Albahari


linq sql .net-4 .net-4.6 linqpad admin

LINQPad 5 (Low-Impact Setup)

  • 1
  • 2
  • 3

5.46.0 | Updated: 09 Apr 2022



Downloads of v 5.46.0:



Software Author(s):

  • Joseph Albahari

  • 1
  • 2
  • 3
LINQPad 5 (Low-Impact Setup) 5.46.0

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests

Validation Testing Passed

Verification Testing Passed


Scan Testing Successful:

No detections found in any package files

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install LINQPad 5 (Low-Impact Setup), run the following command from the command line or from PowerShell:


To upgrade LINQPad 5 (Low-Impact Setup), run the following command from the command line or from PowerShell:


To uninstall LINQPad 5 (Low-Impact Setup), run the following command from the command line or from PowerShell:


Deployment Method:

📝 NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to

2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Copy Your Script

choco upgrade linqpad5.install -y --source="'INTERNAL REPO URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade linqpad5.install -y --source="'INTERNAL REPO URL'" 

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Install linqpad5.install
    name: linqpad5.install
    version: '5.46.0'
    state: present

See docs at

chocolatey_package 'linqpad5.install' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '5.46.0'

See docs at

cChocoPackageInstaller linqpad5.install
    Name     = "linqpad5.install"
    Version  = "5.46.0"
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'linqpad5.install':
  ensure   => '5.46.0',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',

Requires Puppet Chocolatey Provider module. See docs at

4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package is likely a meta/virtual (*) or an installer (*.install) or portable (*.portable) application package.

  • Meta/virtual (*) - has a dependency on the *.install or the *.portable package - it is provided for discoverability and for other packages to take a dependency on.
  • Portable (*.portable/*.commandline (deprecated naming convention)/*.tool (deprecated naming convention)) - usually zips or archives that require no administrative access to install.
  • Install (*.install/*.app (deprecated naming convention)) - uses native installers, usually requires administrative access to install.

Learn more about chocolatey's distinction of installed versus portable apps and/or learn about this kind of package.

This package was approved as a trusted package on 09 Apr 2022.


LINQPad lets you interactively query databases in a modern query language: LINQ. LINQPad supports everything in C# 6.0 and Framework 4.6 (LINQ to Objects, SQL, EF, XML, Parallel LINQ, etc.). It also supports OData, Azure, and a lot more. LINQPad is also a great way to learn LINQ: it comes loaded with 500 examples from the book, C# 6.0 in a Nutshell. And LINQPad is more than a LINQ tool: it's an ergonomic C#/VB/F# scratchpad that instantly executes any expression, statement block or program with rich output formatting – the ultimate in dynamic development.
This package is the low-impact setup, which creates a desktop shortcut and a file association for .LINQ files.


$ErrorActionPreference = 'Stop';

$packageName= 'linqpad5.install'
$url        = ''

$packageArgs = @{
  packageName   = $packageName
  unzipLocation = $toolsDir
  fileType      = 'exe'
  url           = $url
  softwareName  = 'linqpad*'
  checksum      = 'acde8d491da20fd40e9773b030d62fa9feb6d12ce1ff33cf92db6ce51b01ac19'
  checksumType  = 'sha256'
  silentArgs    = "/silent"
  validExitCodes= @(0)

Install-ChocolateyPackage @packageArgs
Install-ChocolateyPath "${env:ProgramFiles(x86)}\LinqPad5"
$ErrorActionPreference = 'Stop'

$toolsDir = "$(Split-Path -Parent $MyInvocation.MyCommand.Definition)"

. $toolsDir\Uninstall-ChocolateyPath.ps1

Uninstall-ChocolateyPath "${env:ProgramFiles(x86)}\LinqPad5"
# Copyright 2011 - Present RealDimensions Software, LLC
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# See the License for the specific language governing permissions and
# limitations under the License.

function Uninstall-ChocolateyPath {
    **NOTE:** Administrative Access Required when `-PathType 'Machine'.`
    This puts a directory to the PATH environment variable of the
    requested scope (Machine or User).
    Removes path from target path scope.  Removes multiple occurances (if they exist)
    and all occurances with or without a trailing slash.
    This command will assert UAC/Admin privileges on the machine if
    `-PathType 'Machine'`.
    This is used when the application/tool is not being linked by Chocolatey
    (not in the lib folder).
    .PARAMETER PathToUninstall
    The full path to a location to remove from the PATH.
    .PARAMETER PathType
    Which PATH to remove it from. If specifying `Machine`, this requires admin
    privileges to run correctly.
    .PARAMETER IgnoredArguments
    Allows splatting with arguments that do not apply. Do not use directly.
    Uninstall-ChocolateyPath -PathToUninstall "$($env:SystemDrive)\tools\gittfs"
    Uninstall-ChocolateyPath "$($env:SystemDrive)\Program Files\MySQL\MySQL Server 5.5\bin" -PathType 'Machine'
        [parameter(Mandatory = $true, Position = 0)][alias("Path")][string] $PathToUninstall,
        [parameter(Mandatory = $false, Position = 1)][ValidateSet('User', 'Machine', 'All')][alias("Scope")][String] $pathType = 'User',
        [parameter(Mandatory = $false)][switch] $RecursiveCall,
        [parameter(ValueFromRemainingArguments = $true)][Object[]] $ignoredArguments
    Write-Debug "Running 'Uninstall-ChocolateyPath' with PathToUninstall:`'$PathToUninstall`'";
    If (!$RecursiveCall -AND ($pathType -ine 'All')) { Write-Host "Only evaluating and updating path scope `"$pathType`", path will not be assessed nor removed for other scope, so path may exist in other scope as well." }
    $originalPathToUninstall = $PathToUninstall
    #First half on handling trailing slash properly - remove it from requested path:
    $PathToUninstall = $PathToUninstall.trimend('\')
    #array drops blanks (one of which is always created by final semi-colon)
    $actualPathArrayUser = (Get-EnvironmentVariable -Name 'Path' -Scope 'user' -PreserveVariables).split(';', [System.StringSplitOptions]::RemoveEmptyEntries)
    $actualPathArrayMachine = (Get-EnvironmentVariable -Name 'Path' -Scope 'machine' -PreserveVariables).split(';', [System.StringSplitOptions]::RemoveEmptyEntries)
    $PathFoundInMachine = $PathFoundInUser = $False
    If (($actualpathArrayMachine -icontains "$($PathToUninstall.ToLower())") -OR ($actualpathArrayMachine -icontains "$(($PathToUninstall + '\').ToLower())")) {
        $PathFoundInMachine = $True
    If (($actualpathArrayUser -icontains "$($PathToUninstall.ToLower())") -OR ($actualpathArrayUser -icontains "$(($PathToUninstall + '\').ToLower())")) {
        $PathFoundInUser = $True
    #Process machine first to minimize suppression of messaging when recursion is necessary to process machine path
    If ($PathFoundInMachine) {
        If (!$RecursiveCall) { Write-Host "Target path `"$PathToUninstall`" exists in Machine scope..." }
        If ($pathType -ieq 'User' -AND ($pathType -ine 'All')) {
            If (!$RecursiveCall) { Write-Host "`"$PathToUninstall`" will only be removed from Machine scope per your request.  Use -PathType 'User' to remove only from Machine scope or -PathType 'All' to remove from all scopes." }
        If (($pathType -ieq 'Machine') -OR ($pathType -ieq 'All')) {
            If (!$RecursiveCall) { Write-Host "PATH environment variable for scope `"Machine`" contains `"$PathToUninstall`". Removing..." }
            $actualpathArray = $actualPathArrayMachine
            [string[]]$Newpatharray = $null
            foreach ($path in $actualpathArray) {
                #second half of handling trailing slash properly - compare to both options in target path
                If (($path -ine "$PathToUninstall") -AND ($path -ine "$($PathToUninstall)\")) {
                    [string[]]$Newpatharray += "$path"
            $actualPath = ($Newpatharray -join (';')) + ';'
            if (Test-ProcessAdminRights) {
                Set-EnvironmentVariable -Name 'Path' -Value $actualPath -Scope 'Machine'
            ElseIf (!$RecursiveCall) {
                $psArgs = "Uninstall-ChocolateyPath -PathToUninstall `'$originalPathToUninstall`' -pathType `'Machine`' -RecursiveCall"
                Start-ChocolateyProcessAsAdmin "$psArgs"
                If ($RecursiveCall) { Return }
            Else {
                Throw "Did not gain admin rights on the recursive call, exiting to avoid going into recursive loop."
    If ($PathFoundInUser) {
        Write-Host "Target path `"$PathToUninstall`" exists in User scope..."
        If ($pathType -ine 'Machine' -AND ($pathType -ine 'All')) {
            Write-Host "`"$PathToUninstall`" will only be removed from User scope per your request.  Use -PathType 'Machine' to remove only from Machine scope or -PathType 'All' to remove from all scopes."
        If (($pathType -ieq 'User') -OR ($pathType -ieq 'All')) {
            Write-Host "PATH environment variable for scope `"User`" contains `"$PathToUninstall`". Removing..."
            $actualpathArray = $actualPathArrayUser
            [string[]]$Newpatharray = $null
            foreach ($path in $actualpathArray) {
                #second half of handling trailing slash properly - compare to both options in target path
                If (($path -ine "$PathToUninstall") -AND ($path -ine "$($PathToUninstall)\")) {
                    [string[]]$Newpatharray += "$path"
            $actualPath = ($Newpatharray -join (';')) + ';'
            Set-EnvironmentVariable -Name 'Path' -Value $actualPath -Scope 'User'
    If ($PathFoundInUser -OR $PathFoundInMachine) {
        Write-Host "Updating environment for current process"
    Else {
        Write-Host "`"$PathToUninstall`" was not found in requested scope `"$PathType`". Nothing to do..."

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Add to Builder Version Downloads Last Updated Status
LINQPad 5 (Low-Impact Setup) 5.44.02 1943 Wednesday, July 21, 2021 Approved
LINQPad 5 (Low-Impact Setup) 5.43.0 2664 Thursday, October 15, 2020 Approved
LINQPad 5 (Low-Impact Setup) 5.41 3811 Monday, February 10, 2020 Approved
LINQPad 5 (Low-Impact Setup) 5.40.0 6063 Monday, August 19, 2019 Approved
LINQPad 5 (Low-Impact Setup) 5.36.03 6965 Monday, November 26, 2018 Approved
LINQPad 5 (Low-Impact Setup) 3283 Friday, July 20, 2018 Approved
LINQPad 5 (Low-Impact Setup) 5.31.0 2542 Wednesday, May 30, 2018 Approved
LINQPad 5 (Low-Impact Setup) 5.26.01 4086 Monday, December 18, 2017 Approved
LINQPad 5 (Low-Impact Setup) 5.25.00 1506 Friday, November 17, 2017 Approved

This package has no dependencies.

Discussion for the LINQPad 5 (Low-Impact Setup) Package

Ground Rules:

  • This discussion is only about LINQPad 5 (Low-Impact Setup) and the LINQPad 5 (Low-Impact Setup) package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or LINQPad 5 (Low-Impact Setup), or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus