Skip to main content

TFS Build vNext–Build tasks cannot handle spaces in repository path

I’m a big fan of the new build system in TFS. However it’s still a learning process for me. After adding the NuGet Packager task, my build failed with the following error message:

1.  T02:04:25.2941286Z Creating Nuget Arguments:
2.  2016-02-08T02:04:25.3019414Z --ARGS: pack d:\b\3\_work\1c61834d\my demo project\NugetSpecs\test1.csproj.nuspec -OutputDirectory d:\b\3\_work\1c61834d\demo -Properties Configuration=Release -version 2016.2.8.1
3.  2016-02-08T02:04:25.3029180Z Invoking nuget with pack d:\b\3\_work\1c61834d\my demo project\NugetSpecs\test2.csproj.nuspec -OutputDirectory d:\b\3\_work\1c61834d\demo -Properties Configuration=Release -version 2016.2.8.1
4.  2016-02-08T02:04:25.3029180Z D:\b\3\agent\worker\tools\NuGet.exe pack d:\b\3\_work\1c61834d\my demo project\NugetSpecs\demo3.csproj.nuspec -OutputDirectory d:\b\3\_work\1c61834d\demo -Properties Configuration=Release -version 2016.2.8.1
5.  2016-02-08T02:04:28.3342844Z pack: invalid arguments.
6.  2016-02-08T02:04:28.3391674Z usage: nuget pack <nuspec | project> [options]
The generated Nuget Pack command is indeed incorrect. Why? Because the task didn’t escape the path to my .nuspec file correctly. As highlighted in yellow, you could see that the path contains some whitespaces. 
I was planning to fix the issue, but thanks to the power of open source, someone already fixed the specific task: https://github.com/Microsoft/vso-agent-tasks/commit/3a7ac0f11ebe17cb110cca904cc8313319c4ad97

But how do I get this updated task on my on premise TFS server?

Here are the steps you need to take:
  • Download and install the TFX command line tool using NPM:
    • npm install -g tfx-cli
  • Before you can use the TFX tool with your on premise TFS server, you have to enable basic authentication:
  • Clone the vso-agent-tasks repository on your local file system
    • Find the path to the task you want to upload
    • In our case this is c:\github\vso-agent-tasks\tasks\NugetPackager
  • Run the TFX tool and specify the path of the specific task
    • ~$ tfx build tasks upload --task-path c:\github\vso-agent-tasks\tasks\NugetPackager
  • You can check that the task is uploaded succesfully by executing the following command
    • ~$ tfx build tasks list

More information:

Popular posts from this blog

DevToys–A swiss army knife for developers

As a developer there are a lot of small tasks you need to do as part of your coding, debugging and testing activities.  DevToys is an offline windows app that tries to help you with these tasks. Instead of using different websites you get a fully offline experience offering help for a large list of tasks. Many tools are available. Here is the current list: Converters JSON <> YAML Timestamp Number Base Cron Parser Encoders / Decoders HTML URL Base64 Text & Image GZip JWT Decoder Formatters JSON SQL XML Generators Hash (MD5, SHA1, SHA256, SHA512) UUID 1 and 4 Lorem Ipsum Checksum Text Escape / Unescape Inspector & Case Converter Regex Tester Text Comparer XML Validator Markdown Preview Graphic Color B

Help! I accidently enabled HSTS–on localhost

I ran into an issue after accidently enabling HSTS for a website on localhost. This was not an issue for the original website that was running in IIS and had a certificate configured. But when I tried to run an Angular app a little bit later on http://localhost:4200 the browser redirected me immediately to https://localhost . Whoops! That was not what I wanted in this case. To fix it, you need to go the network settings of your browser, there are available at: chrome://net-internals/#hsts edge://net-internals/#hsts brave://net-internals/#hsts Enter ‘localhost’ in the domain textbox under the Delete domain security policies section and hit Delete . That should do the trick…

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.