Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

NuGet.exe pack should pack all kinds of projects including .NET Core projects and be consistent with msbuild /t:pack #5918

Closed
anangaur opened this issue Sep 21, 2017 · 2 comments
Closed

NuGet.exe pack should pack all kinds of projects including .NET Core projects and be consistent with msbuild /t:pack #5918

anangaur opened this issue Sep 21, 2017 · 2 comments
Labels
Functionality:Pack Priority:1 High priority issues that must be resolved in the current sprint. Resolution:Duplicate This issue appears to be a Duplicate of another issue Triage:NeedsTriageDiscussion Type:Feature
Milestone
Backlog

Comments

@anangaur
Copy link
Member

anangaur commented Sep 21, 2017 •
edited by rohit21agrawal
Loading

Related issue: #4054 , #4491

Today NuGet.exe pack does not work on PackageReference projects. This has users confused as many users have been using nuget.exe to pack for packages.config and project.json based projects.

The following should just work:

nuget.exe pack <project>.csproj
nuget.exe pack <name>.nuspec
@rohit21agrawal rohit21agrawal mentioned this issue Sep 22, 2017
Closed
@rrelyea rrelyea added this to the Backlog milestone Sep 25, 2017
@rrelyea rrelyea added Triage:NeedsTriageDiscussion Priority:1 High priority issues that must be resolved in the current sprint. Type:Feature and removed 0 - Backlog labels Sep 25, 2017
@rohit21agrawal rohit21agrawal changed the title NuGet.exe pack should pack all kinds of projects including .NET Core projects NuGet.exe pack should pack all kinds of projects including .NET Core projects and be consistent with msbuild /t:pack Oct 4, 2017
@rohit21agrawal rohit21agrawal mentioned this issue Oct 4, 2017
Closed
@MJeorrett
Copy link

This is causing issues for us as we are wanting to create nuget packages in VSTS build. Only the "Nuget pack" step supports auto setting the version number so I am probably going to have to use something like this in the meantime to set the version with a powershell script. Whilst this is useful in the short term, being able to set the version automatically via a standard build step is obviously required mid to long term.

@nkolev92 nkolev92 added the Resolution:Duplicate This issue appears to be a Duplicate of another issue label Oct 17, 2017
@nkolev92
Copy link
Member

Closing this in favor of #4491.

Both of the aforementioned issues are also tracked in #5877

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Functionality:Pack Priority:1 High priority issues that must be resolved in the current sprint. Resolution:Duplicate This issue appears to be a Duplicate of another issue Triage:NeedsTriageDiscussion Type:Feature
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
4 participants
@nkolev92 @rrelyea @MJeorrett @anangaur