Closed siennathesane closed 5 years ago
@devlead Where is the best place to put a unit test with a custom build.cake to provoke this issue?
@Roadrunner67 Try quoting the target: .\build.ps1 -Target "Project.DevServer"
and see if it works. Looks like the command line arguments sent to the program sees Project.DevServer
as two arguments.
Quotes don't help. The VS Code Cake extension already quotes the targets BTW.
OK, the problem lies with build.ps1 if I call cake.exe directly it is a non-issue.
Build.ps1 line 246:
$cakeArguments = @("$Script"); if ($Target) { $cakeArguments += "-target=""$Target""" } if ($Configuration) { $cakeArguments += "-configuration=$Configuration" }
..instead of..
$cakeArguments = @("$Script"); if ($Target) { $cakeArguments += "-target=$Target" } if ($Configuration) { $cakeArguments += "-configuration=$Configuration" }
.. fixes the problem - not sure where build. ps1 lives though
@Roadrunner67 the bootstrappers reside in the https://github.com/cake-build/resources/ repo.
@devlead my PR #79 fails on AppVeyor, but I have no clue what the problem is.
Looks like it fails if no script is supplied.
@devlead ok, got it - ready for approval
fixed by #80
What You Are Seeing?
More than one build script specified.
What is Expected?
Able to have a task name reflect a dotnet project name which contains a period; i.e.
Project.Identifier
.What version of Cake are you using?
0.33.0
Are you running on a 32 or 64 bit system?
64-bit
What environment are you running on? Windows? Linux? Mac?
Are you running on a CI Server? If so, which one?
No, local with both PS Core and PS Framework.
How Did You Get This To Happen? (Steps to Reproduce)