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.

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

Make 'dotnet list package' machine-readable #9524

Closed
zarenner opened this issue May 4, 2020 · 1 comment
Closed

Make 'dotnet list package' machine-readable #9524

zarenner opened this issue May 4, 2020 · 1 comment
Labels
Functionality:ListPackage dotnet.exe list package Product:dotnet.exe Resolution:Duplicate This issue appears to be a Duplicate of another issue Type:Feature

Comments

@zarenner
Copy link

zarenner commented May 4, 2020

The output of dotnet list package today looks like:

Project 'foo.csproj' has the following package references
   [netstandard2.0]:
   Top-level Package                                Requested         Resolved
   > SomePackage                                    [1.1.6]           1.1.6

It would be useful if there was a machine-readable output format. This is useful for various scenarios such as gathering OSS license information based on packages used.

@zarenner zarenner changed the title 'dotnet list package' Make 'dotnet list package' machine-readable May 4, 2020
@nkolev92
Copy link
Member

nkolev92 commented May 5, 2020

Duplicate of #7752

@nkolev92 nkolev92 marked this as a duplicate of #7752 May 5, 2020
@nkolev92 nkolev92 closed this as completed May 5, 2020
@nkolev92 nkolev92 added Functionality:ListPackage dotnet.exe list package Product:dotnet.exe Type:Feature Resolution:Duplicate This issue appears to be a Duplicate of another issue labels May 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Functionality:ListPackage dotnet.exe list package Product:dotnet.exe Resolution:Duplicate This issue appears to be a Duplicate of another issue Type:Feature
Projects
None yet
Development

No branches or pull requests

2 participants