Comments on: How to use a tool installed by Nuget in your build scripts http://lostechies.com/joshuaflanagan/2011/06/24/how-to-use-a-tool-installed-by-nuget-in-your-build-scripts/ Thu, 14 Mar 2013 03:50:00 +0000 hourly 1 http://wordpress.org/?v=3.4.2 By: Mark http://lostechies.com/joshuaflanagan/2011/06/24/how-to-use-a-tool-installed-by-nuget-in-your-build-scripts/#comment-291 Mark Tue, 18 Dec 2012 20:26:00 +0000 http://lostechies.com/joshuaflanagan/2011/06/24/how-to-use-a-tool-installed-by-nuget-in-your-build-scripts/#comment-291 I found an easier fix. Apparently 'CD" does work with wildcards. So in your build event you do: CD "$(SolutionDir)packagesMyAwesomeTool*tools" CALL MyAwesomeTool.cmd I found an easier fix. Apparently ‘CD” does work with wildcards. So in your build event you do:
CD “$(SolutionDir)packagesMyAwesomeTool*tools”
CALL MyAwesomeTool.cmd

]]> By: Ray O'Neill http://lostechies.com/joshuaflanagan/2011/06/24/how-to-use-a-tool-installed-by-nuget-in-your-build-scripts/#comment-182 Ray O'Neill Sun, 26 Jun 2011 15:07:00 +0000 http://lostechies.com/joshuaflanagan/2011/06/24/how-to-use-a-tool-installed-by-nuget-in-your-build-scripts/#comment-182 top-of-my-head powershell version, save as nunit.ps1 in root directory $filename = $args[0]$scriptDir = [System.IO.Path]::GetDirectoryName($myInvocation.MyCommand.Definition)$packagesDir = Join-Path $scriptDir "sourcepackages"$exePath = dir $packagesDir -recurse | where { $_.PSIsContainer -eq $false -and $_.Name -eq $filename } | foreach { $_.FullName } | sort -descending | select -first 1$argString = ""for($count = 1; $count -lt $args.Length; $count++){    $argString = $argString + $args[$count]}$cmdline = $exePath + " " + $argStringInvoke-Expression $cmdline Then your build can call powershell.exe full-path-to-nunit.ps1 nunit-console.exe arg1 arg2 arg3 '`"arg with spaces`"' Probably a billion ways to do this. Thanks for occupying my Sunday morning :) top-of-my-head powershell version, save as nunit.ps1 in root directory
$filename = $args[0]$scriptDir = [System.IO.Path]::GetDirectoryName($myInvocation.MyCommand.Definition)$packagesDir = Join-Path $scriptDir “sourcepackages”$exePath = dir $packagesDir -recurse | where { $_.PSIsContainer -eq $false -and $_.Name -eq $filename } | foreach { $_.FullName } | sort -descending | select -first 1$argString = “”for($count = 1; $count -lt $args.Length; $count++){    $argString = $argString + $args[$count]}$cmdline = $exePath + ” ” + $argStringInvoke-Expression $cmdline

Then your build can call powershell.exe full-path-to-nunit.ps1 nunit-console.exe arg1 arg2 arg3 ‘`”arg with spaces`”‘
Probably a billion ways to do this. Thanks for occupying my Sunday morning :)

]]>