Skip to content

Commit

Permalink
Fixed issue with psake.ps1 failing when passing named parameters.
Browse files Browse the repository at this point in the history
  • Loading branch information
JamesKovacs committed Apr 28, 2010
1 parent 21d7cd5 commit 64ea235
Showing 1 changed file with 24 additions and 10 deletions.
34 changes: 24 additions & 10 deletions psake.ps1
@@ -1,14 +1,28 @@
# Helper script for those who want to run psake without importing the module.
# Example:
# .\psake.ps1 "default.ps1" "BuildHelloWord" "4.0"
#
try
{
$scriptPath = Split-Path -parent $MyInvocation.InvocationName;
import-module (join-path $scriptPath psake.psm1)
invoke-psake @args
}
finally
{
remove-module psake -ea "SilentlyContinue"

# Must match parameter definitions for psake.psm1/invoke-psake
# otherwise named parameter binding fails
param(
[Parameter(Position=0,Mandatory=0)]
[string]$buildFile = 'default.ps1',
[Parameter(Position=1,Mandatory=0)]
[string[]]$taskList = @(),
[Parameter(Position=2,Mandatory=0)]
[string]$framework = '3.5',
[Parameter(Position=3,Mandatory=0)]
[switch]$docs = $false,
[Parameter(Position=4,Mandatory=0)]
[System.Collections.Hashtable]$parameters = @{},
[Parameter(Position=5, Mandatory=0)]
[System.Collections.Hashtable]$properties = @{}
)

try {
$scriptPath = Split-Path -parent $MyInvocation.InvocationName;
import-module (join-path $scriptPath psake.psm1)
invoke-psake $buildFile $taskList $framework $docs $parameters $properties
} finally {
remove-module psake -ea "SilentlyContinue"
}

0 comments on commit 64ea235

Please sign in to comment.