Output paths are logged as relative paths #91

New Issue

claunia · 2026-01-29T16:29:18Z

claunia commented

2026-01-29 16:29:18 +00:00

Originally created by @AnthonyMastrean on GitHub (Dec 9, 2020).

The output flag writes to an unexpected relative directory (see #176) and prints the relative path to the screen, which doesn't help to find that directory! Can we have the complete path printed, like the other dotnet CLI commands?

$ dotnet tarball -c Release -o out src/Example/Example.csproj
dotnet tarball (0.1.189+6ef34e121b)
Microsoft (R) Build Engine version 16.6.0+5ff7b0c9e for .NET Core
Copyright (C) Microsoft Corporation. All rights reserved.

  Example -> C:\Users\anthony\example-project\src\Example\bin\Release\netcoreapp3.1\Example.dll
  Example -> C:\Users\anthony\example-project\src\Example\bin\Release\netcoreapp3.1\publish
  Creating tarball out\Example.0.0.0.tar.gz

For example, the output might look like this:

$ dotnet tarball -c Release -o out src/Example/Example.csproj
dotnet tarball (0.1.189+6ef34e121b)
Microsoft (R) Build Engine version 16.6.0+5ff7b0c9e for .NET Core
Copyright (C) Microsoft Corporation. All rights reserved.

  Example -> C:\Users\anthony\example-project\src\Example\bin\Release\netcoreapp3.1\Example.dll
  Example -> C:\Users\anthony\example-project\src\Example\bin\Release\netcoreapp3.1\publish
  Creating tarball C:\Users\anthony\example-project\src\Example\out\Example.0.0.0.tar.gz

Originally created by @AnthonyMastrean on GitHub (Dec 9, 2020). The `output` flag writes to an unexpected relative directory (see #176) and prints the relative path to the screen, which doesn't help to find that directory! Can we have the complete path printed, like the other `dotnet` CLI commands? ``` $ dotnet tarball -c Release -o out src/Example/Example.csproj dotnet tarball (0.1.189+6ef34e121b) Microsoft (R) Build Engine version 16.6.0+5ff7b0c9e for .NET Core Copyright (C) Microsoft Corporation. All rights reserved. Example -> C:\Users\anthony\example-project\src\Example\bin\Release\netcoreapp3.1\Example.dll Example -> C:\Users\anthony\example-project\src\Example\bin\Release\netcoreapp3.1\publish Creating tarball out\Example.0.0.0.tar.gz ``` For example, the output might look like this: ``` $ dotnet tarball -c Release -o out src/Example/Example.csproj dotnet tarball (0.1.189+6ef34e121b) Microsoft (R) Build Engine version 16.6.0+5ff7b0c9e for .NET Core Copyright (C) Microsoft Corporation. All rights reserved. Example -> C:\Users\anthony\example-project\src\Example\bin\Release\netcoreapp3.1\Example.dll Example -> C:\Users\anthony\example-project\src\Example\bin\Release\netcoreapp3.1\publish Creating tarball C:\Users\anthony\example-project\src\Example\out\Example.0.0.0.tar.gz ```

claunia added the up-for-grabs bug labels 2026-01-29 16:29:19 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/dotnet-packaging#91