Creating and Publishing to NuGet

Now that we have a Nuget Server installed and up and running we will want to deploy our packages.

First you’ll need to install the nuget.exe command line bootstrapper

Installing NuGet.exe

  • Download NuGet.exe
  • Place NuGet in a well known location such as c:\utils on your machine
  • Make sure that NuGet.exe is in your path

Then you can take two simple steps to generate your package

nuget pack MyProject.csproj -IncludeReferencedProjects -Prop Configuration=Release

then push your pack to the nuget server, with your APIKey you setup in your web.config of the nuget.server

nuget push {package file} -s http://yourNugetServer/ {apikey}

That is it, you now have your package available in your own private nuget server.

For more details on Creating and Publishing a Package

Setting up a NuGet Server

Whether it’s your company restricts which third-party libraries their developers may use or just you need your own private repository to store all your protected work.  A NuGet Server is what you are after.

Before I start I need to mention a few things about NuGet Gallery, which I spent a good two days trying to get working correctly on Azure and failed and in the end ended up generating a very basic Nuget Server to host all the libraries.

This all can be done with just four simple steps

  1. Create a new DotNet Core Web MVC Application
  2. Install nuget.server (
  3. Deploy your application to your website

That is it, if you fire up your server you should see a screen like this:

That is it you now have a hosted Nuget Server, next we’ll look at deploying your solution to the Nuget Server

Full details can be found here: Host Your Own NuGet Server or How To Create Local NuGet Server

User Stories

Here are some helpful pointers for writing User Stories

Story template
  1. “As a <User or role>
  2. I want <Business Functionality>
  3. So that <Business Justification>”
  1. As a Account Holder,
  2. I want to be able to withdraw funds from my checking account,
  3. So that I can buy some bling.
Stories are not
  • “mini” Use Cases
  • a complete specification
  • a contract
  • intended to be interpreted without a Product Owner
User Stories guidelines
  • Testable – Tangible acceptance tests can be written against any delivered software
  • The scope of the User Story is manage-able enough for the team to provide an Estimate
  • Independent and do not rely on other Stories
  • Sized appropriately.. Have a level of effort which the team can comfortably achieve in the duration of a single iteration