New Post: Scenarios to create packages are not smooth

@dotnetjunky I don't have a specific list of problems. Our enterprise customers have reported that PACK[csproj] is generally problematic outside of simple scenarios, and while it's entirely possible that it's a PEBKAC issue, our users are generally sophisticated.

However, our recommendation not to use PACK[csproj] is less based on reported problems, and more on enterprise process/workflow best practices. The proper workflow for packaging a dependency is:

1. Label/Tag Source
2. Get Source
3. Build
4. Run Unit Tests, static analysis, etc
5. Package
   

nuget.exe fits only into step 5 (and obviously later when publishing). Of course it can also (try to) fit in steps 3 and 4, but with a sufficient amount of VBA, so could Microsoft Excel. FWIW, MAVEN (tries to) do not only 1-5, but steps 6+ as well. It fails just as spectacularly, which is we we also recommend MAVEN in Step 5 only as well.

nuget.exe is a specific type of hammer, and it doesn't pound in screws very well. Thus, our recommendation for PACK[csproj] is that it's fine for simple projects you build on your desktop, but it's inappropriate in enterprise development practices.