.NET Core–Push Nuget Package After Build

October 26, 2017 · 1 min read

You can configure.NET Core to automatically push your nuget package to the package server of your choice by adding a Target to your project file.

  1. If your package server requires an api key, you can set it by calling

nuget.exe SetApiKey

  1. Add the following target to your csproj file.   This sample is configured to only fire on Release Builds.

                        

OR

Here’s a version that will ensure releases with a.0 revision number are properly pushed.

    < GetAssemblyIdentity AssemblyFiles="$(TargetPath)">               < PropertyGroup>       < vMajor>$(\[System.Version\]::Parse(%(AssemblyVersion.Version)).Major)       < vMinor>$(\[System.Version\]::Parse(%(AssemblyVersion.Version)).Minor)       < vBuild>$(\[System.Version\]::Parse(%(AssemblyVersion.Version)).Build)       < vRevision>$(\[System.Version\]::Parse(%(AssemblyVersion.Version)).Revision)                  
This article is part of the GWB Archives. Original Author: ChrisD

New on Geeks with Blogs

  • We Won The One Award I Actually Care About

    Full Scale made the Inc. 5000 for the fifth year straight, the 12th listing across my three companies. Here is why the one award you cannot buy is worth stopping for.

  • Your Customers Build the Features Now

    I let a tool I liked sit dead for a year rather than build the features I wanted. An MCP server meant I never had to, and your customers can do the same to your product.

  • Get the Size of a Directory in Linux the Easy Way

    du -sh for the quick answer, ncdu for the cleanup, df for the disk itself: every command for checking directory size in Linux, plus why du and df never agree.

  • Vim Search and Replace: The Ultimate Guide

    One :%s command replaces every match in a file before a find dialog would even open. The Vim substitute patterns worth the muscle memory: flags, ranges, capture groups, and multi-file edits.