Streamlined Package Creation Workflow

Current behavior (NuGet 1.2)

Package creation today using NuGet.exe requires assembling binaries and content files in a convention based folder structure and then running the nuget pack command. But most packages are directly packaging the output of a class library. Wouldn’t it be nice to point nuget pack to a csproj?

Scenarios

List of different scenarios a user might want to accomplish.

  1. TBD
  2. TBD

Solution

TBD

Design

Elegant

Symbol Server Integration

TBD

Last edited Apr 4, 2011 at 11:17 PM by haacked, version 3