tag:help.appveyor.com,2012-11-13:/discussions/problems/16271-nuget-not-being-pushed-to-nugetorgAppVeyor: Discussion 2018-10-31T21:00:37Ztag:help.appveyor.com,2012-11-13:Comment/459978362018-08-30T20:42:10Z2018-08-30T20:42:10ZNuget not being pushed to nuget.org<div><p>You need to first make sure that your artifacts are pushed to storage before deploying them via nuget. You need some section in your yaml config file declaring which artifacts to push.Something as simple as this should work.<br></p>
<pre>
<code>artifacts:
- path: '***.nupkg'</code>
</pre></div>Owen McDonnelltag:help.appveyor.com,2012-11-13:Comment/459978362018-08-30T21:11:03Z2018-08-30T21:11:03ZNuget not being pushed to nuget.org<div><p>Got it, thank you, Owen. I wonder my other project works without it.. Maybe because it's using a csproj vs sln and the .nuspec is right next to it?</p></div>Mark Vulfsontag:help.appveyor.com,2012-11-13:Comment/459978362018-08-30T23:32:36Z2018-08-30T23:32:36ZNuget not being pushed to nuget.org<div><p>Well, there is another way as well, which is just to add <code>publish_nuget: true</code> in <code>build:</code> section. Perhaps that's the method you use in the other project?</p></div>Owen McDonnelltag:help.appveyor.com,2012-11-13:Comment/459978362018-08-31T01:18:14Z2018-08-31T01:18:14ZNuget not being pushed to nuget.org<div><p>By that, I mean you can forego the manual nuget packaging step in <code>after_build:</code> section and artifact packaging. This way you can leverage the 1st class support for .NET projects that AppVeyor offers.</p></div>Owen McDonnell