We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
$nugetChocolateyPath = (Split-Path -parent $MyInvocation.MyCommand.Definition) $nugetPath = (Split-Path -Parent $nugetChocolateyPath) $nugetExePath = Join-Path $nuGetPath 'bin' $nugetLibPath = Join-Path $nuGetPath 'lib' $badLibPath = Join-Path $nuGetPath 'lib-bad' $extensionsPath = Join-Path $nugetPath 'extensions' $chocInstallVariableName = "ChocolateyInstall" $nugetExe = Join-Path $nugetChocolateyPath 'nuget.exe' $7zip = Join-Path $nugetChocolateyPath 'tools\7za.exe' $ShimGen = Join-Path $nugetChocolateyPath 'tools\shimgen.exe' $checksumExe = Join-Path $nugetChocolateyPath 'tools\checksum.exe'
Some or all of these were used. We'll let the automoderation service pick up and report on these issues.
The text was updated successfully, but these errors were encountered:
(GH-267) Make some variables available again.
6de64c8
Deprecation message will follow through regular messages later so folks can be warned about cleaning these up.
Merge branch 'stable'
a7de809
* stable: (GH-124) Allow posh extensions from assemblies (GH-264) Do not fail if shortcut creation fails (GH-267) Make some variables available again.
Looks like $nugetExePath is also in Install-ChocolateyPowerShellCommand.ps1 helper
$nugetExePath
Install-ChocolateyPowerShellCommand.ps1
Sorry, something went wrong.
ferventcoder
No branches or pull requests
Some or all of these were used. We'll let the automoderation service pick up and report on these issues.
The text was updated successfully, but these errors were encountered: