dotnet pack no longer reports the .nupkg path

[joelverhagen]

NuGet Product(s) Affected

dotnet.exe

Current Behavior

.NET 9.0.100

.NET 8.0.404

Desired Behavior

In .NET 6 SDK this worked fine and I thought it used to work in older versions of NET 8 SDK, but I don't have an older version.

.NET 6.0.428

Additional Context

No response

[baronfel]

This one is blocked in Terminal Logger until we complete dotnet/msbuild#9608, at which point we will have a compatible, declarative way for Targets like Pack to declare their outputs so we can report them in a unified way, instead of the ad-hoc reporting we've done to date.

[baronfel]

In the interim, I believe that message should come back even on terminal logger if you add -v d to the pack command.

EDIT: yes, that is indeed the case, here's the output from me packing FsAutoComplete:

> dotnet pack -v d
Paket version 9.0.2+a9b12aaeb8d8d5e47a415a3442b7920ed04e98e0
Paket version 9.0.2+a9b12aaeb8d8d5e47a415a3442b7920ed04e98e0
Paket version 9.0.2+a9b12aaeb8d8d5e47a415a3442b7920ed04e98e0
Paket version 9.0.2+a9b12aaeb8d8d5e47a415a3442b7920ed04e98e0
The last full restore is still up to date. Nothing left to do.
The last full restore is still up to date. Nothing left to do.
The last full restore is still up to date. Nothing left to do.
The last full restore is still up to date. Nothing left to do.
Total time taken: 0 milliseconds
Total time taken: 0 milliseconds
Total time taken: 0 milliseconds
Total time taken: 0 milliseconds
Paket version 9.0.2+a9b12aaeb8d8d5e47a415a3442b7920ed04e98e0
Paket version 9.0.2+a9b12aaeb8d8d5e47a415a3442b7920ed04e98e0
The last full restore is still up to date. Nothing left to do.
The last full restore is still up to date. Nothing left to do.
Total time taken: 0 milliseconds
Total time taken: 0 milliseconds
Paket version 9.0.2+a9b12aaeb8d8d5e47a415a3442b7920ed04e98e0
Paket version 9.0.2+a9b12aaeb8d8d5e47a415a3442b7920ed04e98e0
Paket version 9.0.2+a9b12aaeb8d8d5e47a415a3442b7920ed04e98e0
Paket version 9.0.2+a9b12aaeb8d8d5e47a415a3442b7920ed04e98e0
The last full restore is still up to date. Nothing left to do.
The last full restore is still up to date. Nothing left to do.
The last full restore is still up to date. Nothing left to do.
The last full restore is still up to date. Nothing left to do.
Total time taken: 0 milliseconds
Total time taken: 0 milliseconds
Total time taken: 0 milliseconds
Total time taken: 0 milliseconds
Restore complete (4.0s)
    Determining projects to restore...
    Restored E:\Code\FsAutoComplete\test\FsAutoComplete.DependencyManager.Dummy\FsAutoComplete.DependencyManager.Dummy.fsproj (in 616 ms).
    Restored E:\Code\FsAutoComplete\src\FsAutoComplete.Logging\FsAutoComplete.Logging.fsproj (in 616 ms).
    Restored E:\Code\FsAutoComplete\test\OptionAnalyzer\OptionAnalyzer.fsproj (in 699 ms).
    Restored E:\Code\FsAutoComplete\src\FsAutoComplete.Core\FsAutoComplete.Core.fsproj (in 1.15 sec).
    Restored E:\Code\FsAutoComplete\benchmarks\benchmarks.fsproj (in 1.15 sec).
    Restored E:\Code\FsAutoComplete\src\FsAutoComplete\FsAutoComplete.fsproj (in 1.15 sec).
    Restored E:\Code\FsAutoComplete\test\FsAutoComplete.Tests.Lsp\FsAutoComplete.Tests.Lsp.fsproj (in 1.15 sec).
You are using a preview version of .NET. See: https://aka.ms/dotnet-support-policy
  FsAutoComplete.Logging succeeded (2.3s) → src\FsAutoComplete.Logging\bin\Release\net6.0\FsAutoComplete.Logging.dll
    You are using a preview version of .NET. See: https://aka.ms/dotnet-support-policy
  FsAutoComplete.Core net8.0 succeeded (13.7s) → src\FsAutoComplete.Core\bin\Release\net8.0\FsAutoComplete.Core.dll
    You are using a preview version of .NET. See: https://aka.ms/dotnet-support-policy
  FsAutoComplete net8.0 succeeded (14.2s) → src\FsAutoComplete\bin\Release\net8.0\fsautocomplete.dll
  FsAutoComplete succeeded (2.1s)
    Paket version 9.0.2+a9b12aaeb8d8d5e47a415a3442b7920ed04e98e0
    Total time taken: 0 milliseconds
    Successfully created package 'E:\Code\FsAutoComplete\src\FsAutoComplete\bin\Release\fsautocomplete.0.75.0.nupkg'.

Build succeeded in 37.2s

[baronfel]

@joelverhagen if you felt like it and wanted to help us out to make it easier to do a short-term workaround, if this message Had an MSBuild Code or something on it that we could detect, we could do the same workaround for Pack that we've done for build/publish for output detection.

[joelverhagen]

I will let client team assess whether this needs a workaround or not. It just was a minor paper cut while I was pair programming with someone. I wanted to immediately copy the package path for a subsequent dotnet nuget push call.