Home → Problems →

Build failing when attempting to create a NuGet package

• Edit

Shayne van Asperen

May 18, 2016 @ 06:05 PM

Hello,

I have a build that used to work fine and is now suddenly failing when attempting to create a NuGet package. This is the project I'm having problems with:

https://ci.appveyor.com/project/shaynevanasperen/quarks/build/40

When I run this command locally (pt.bat) it works fine, but not when I run it on AppVeyor. The whole reason I created this build system using PowerShell was to avoid this exact problem of no being able to locally reproduce the build EXACTLY as it works on the build server. What "magic" is going on behind the scenes which is preventing me from achieving this?

1. 1 Posted by Shayne van Aspe... on May 18, 2016 @ 06:10 PM

   

   If I switch to using "Previous Visual Studio 2015" as the build worker image then it works. What magic is going on here?

   • Edit

2. Support Staff 2 Posted by Feodor Fitsner on May 18, 2016 @ 06:23 PM

   

   It was nuget 3.4.3 installed on build worker. This might be an issue, but you can roll back to 3.3 with a simple PS script:

   if (Test-Path 'C:\Tools\NuGet3') { $nugetDir = 'C:\Tools\NuGet3' } else { $nugetDir = 'C:\Tools\NuGet' }
   (New-Object Net.WebClient).DownloadFile('https://dist.nuget.org/win-x86-commandline/v3.3.0/nuget.exe', "$nugetDir\NuGet.exe")
   

   • Edit

3. 3 Posted by Shayne van Aspe... on May 18, 2016 @ 06:41 PM

   

   Thank you. In my further testing of this, I have found the problem. The latest version of NuGet fails if the .nuspec file contains escape characters for greater-than or less-than characters, which I was using to describe generic types in the description tag of the .nuspec file.

   • Edit

4. Ilya Finkelshteyn closed this discussion on Aug 25, 2018 @ 02:06 AM.