Nuspec not being built

Nathan Baulch's Avatar

Nathan Baulch

02 Jun, 2014 02:26 PM

I have a valid nuspec file in the root of my GitHub repository and I've checked the "Package NuGet projects" option, however no matter what I try I can't seem to get a nupkg artifact to appear. What am I missing?

  1. Support Staff 1 Posted by Feodor Fitsner on 02 Jun, 2014 04:24 PM

    Feodor Fitsner's Avatar

    Hi Nathan,

    Automatic NuGet packaging is built around VS project and the idea is that you have .nuspec file (with the same name as project) in the root of your project, not repo. This way AppVeyor could call nuget pack your-project.csproj to build a package.

    Otherwise, you can call nuget pack your-package.nuspec as a build script (or as part of after build scripts) to build a package.

    Please let me know if you have any questions.

  2. 2 Posted by Nathan Baulch on 03 Jun, 2014 01:59 PM

    Nathan Baulch's Avatar

    Thanks, it sounds like I need to move to the scripting approach.

    When I moved my nuspec file into the directory with my project files, AppVeyor tried to build separate packages for all my projects rather than just building the single nuspec project. This is a problem because I have one project file for each target framework (eg, Net20, Net40, Portable, WinFX, etc, see here) that I need bundled into a single NuGet package. Right now my AppVeyor project builds are failing because all these separate NuGet packages files have the same file name.

    Anyway, there definitely needs to be more documentation around this functionality.

  3. Support Staff 3 Posted by Feodor Fitsner on 03 Jun, 2014 05:08 PM

    Feodor Fitsner's Avatar

    Yeah, I agree it might be better using script approach to build multiple packages.
    ...and yes AV docs will be improved.

  4. Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:44 AM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac