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

v9 SDK doesn't print nupkg path on dotnet pack #43248

Closed
AArnott opened this issue Sep 5, 2024 · 3 comments
Closed

v9 SDK doesn't print nupkg path on dotnet pack #43248

AArnott opened this issue Sep 5, 2024 · 3 comments
Labels
Area-CLI untriaged Request triage from a team member

Comments

@AArnott
Copy link
Contributor

AArnott commented Sep 5, 2024

Describe the bug

All prior versions of the .NET SDK printed the path of a built .nupkg. But the v9 preview hides this, favoring to only print the path to the built .dll.

To Reproduce

dotnet new classlib -o tst
cd tst
dotnet pack

Actual output

Restore complete (0.3s)
You are using a preview version of .NET. See: https://aka.ms/dotnet-support-policy
  tst succeeded (2.2s) → bin\Release\net9.0\tst.dll

Build succeeded in 2.9s

Workload updates are available. Run `dotnet workload list` for more information.

Expected output

Since this was a dotnet pack command, I expect to see the path to the package.

Restore complete (0.3s)
You are using a preview version of .NET. See: https://aka.ms/dotnet-support-policy
  tst succeeded (2.2s) → artifacts\Debug\packages\tst.1.0.0.nupkg

Build succeeded in 2.9s

Workload updates are available. Run `dotnet workload list` for more information.

Further technical details

9.0.100-preview.7.24407.12

@dotnet-issue-labeler dotnet-issue-labeler bot added Area-CLI untriaged Request triage from a team member labels Sep 5, 2024
@baronfel
Copy link
Member

baronfel commented Sep 5, 2024

This is a gap in terminal logger. We're tracking an issue in MSBuild about generalizing the "output detection" mechanism that tasks can use. We could potentially try to special case pack here in the short term, but we were hoping to have something generalized before too much longer.

@rainersigwald

@rainersigwald
Copy link
Member

We should special-case it for 9 IMO

@marcpopMSFT
Copy link
Member

looks like there's already a tracking issue in msbuild so closing here.

@marcpopMSFT marcpopMSFT closed this as not planned Won't fix, can't repro, duplicate, stale Sep 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-CLI untriaged Request triage from a team member
Projects
None yet
Development

No branches or pull requests

4 participants