Fix for chocolateyInstall and version bump to 4.2

NuGetPackageBuilder.ps1

@@ -0,0 +1,13 @@
+# Assumes robocopy on the path
+
+$scriptpath = $MyInvocation.MyCommand.Path
+$dir = Split-Path $scriptpath
+$destDir = "$dir\bin"
+if(Test-Path $destDir -PathType container){
+	Remove-Item $destDir -Recurse -Force
+}
+
+robocopy $dir "$destDir\tools" /E /B /NP /R:0 /W:0 /NJH /NJS /NS /NFL /NDL /XF ".git*" "Nuget*" "*.nupkg"  /XD "$dir\nuget" "$dir\.git" "$destDir" "$dir\nuget.exe"
+robocopy "$dir\nuget" $destDir /E /B /NP /R:0 /W:0 /NJH /NJS /NS /NFL /NDL
+
+.\nuget pack "$destDir\psake.nuspec"

nuget/psake.nuspec

@@ -2,7 +2,7 @@
 <package xmlns="http://schemas.microsoft.com/packaging/2010/07/nuspec.xsd">
   <metadata>
     <id>psake</id>
-    <version>4.1.0</version>
+    <version>4.2.0.1</version>
     <authors>James Kovacs</authors>
     <owners>James Kovacs, Damian Hickey, Rob Reynolds</owners>
     <projectUrl>https://github.com/psake/psake</projectUrl>

nuget/tools/chocolateyInstall.ps1

@@ -1,14 +1,19 @@
-$nugetPath = 'C:\NuGet'
-$nugetExePath = Join-Path $nuGetPath 'bin'
-$packageBatchFileName = Join-Path $nugetExePath "psake.bat"
+try { 
+  $nugetPath = $env:ChocolateyInstall
+  $nugetExePath = Join-Path $nuGetPath 'bin'
+  $packageBatchFileName = Join-Path $nugetExePath "psake.bat"
 
-$psakeDir = (Split-Path -parent $MyInvocation.MyCommand.Definition)
-#$path = ($psakeDir | Split-Path | Join-Path -ChildPath  'psake.cmd')
-$path = Join-Path $psakeDir  'psake.cmd'
-Write-Host "Adding $packageBatchFileName and pointing to $path"
-"@echo off
-""$path"" %*" | Out-File $packageBatchFileName -encoding ASCII 
+  $psakeDir = (Split-Path -parent $MyInvocation.MyCommand.Definition)
+  #$path = ($psakeDir | Split-Path | Join-Path -ChildPath  'psake.cmd')
+  $path = Join-Path $psakeDir  'psake.cmd'
+  Write-Host "Adding $packageBatchFileName and pointing to $path"
+  "@echo off
+  ""$path"" %*" | Out-File $packageBatchFileName -encoding ASCII 
 
+  write-host "PSake is now ready. You can type 'psake' from any command line at any path. Get started by typing 'psake /?'"
 
-write-host "PSake is now ready. You can type 'psake' from any command line at any path. Get started by typing 'psake /?'"
-Start-Sleep 6
+  Write-ChocolateySuccess 'psake'
+} catch {
+  Write-ChocolateyFailure 'psake' "$($_.Exception.Message)"
+  throw 
+}

psake.psm1

@@ -681,7 +681,7 @@ convertfrom-stringdata @'
 import-localizeddata -bindingvariable msgs -erroraction silentlycontinue
 
 $script:psake = @{}
-$psake.version = "4.1.0" # contains the current version of psake
+$psake.version = "4.2.0" # contains the current version of psake
 $psake.context = new-object system.collections.stack # holds onto the current state of all variables
 $psake.run_by_psake_build_tester = $false # indicates that build is being run by psake-BuildTester
 $psake.config_default = new-object psobject -property @{