Azure-devops-docs: Why is there a ".NET Core CLI" help page ?

Created on 11 Oct 2018  Â·  4Comments  Â·  Source: MicrosoftDocs/azure-devops-docs

All information which is defined on this page (https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/build/dotnet-core-cli?view=vsts) is also explained on (https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/build/dotnet-core?view=vsts)

So what is the reason for this page ?
Maybe better to remove this page and rename .NET Core page to .NET Core CLI ?


Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

devopprod doc-bug

All 4 comments

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Bump this.
I spent hours referring to Azure DevOps > Build Pipelines > Reference > Tasks > Build Tasks > .NET Core CLI trying to solve an issue that had a solution laid out in Azure DevOps > Build Pipelines > Reference > Tasks > Build Tasks > .NET Core. They both reference the same tool. The page separation makes sense if .NET Core Cli stays the same and .NET Core is renamed to .NET Core Cli Usage and the pages are linked with each other internally.

I created an issue on the task repo while trying to solve the issue and updated when I found the correct documentation.
https://github.com/microsoft/azure-pipelines-tasks/issues/10507

Thanks for reporting this issue, we are looking into this.
@pulkitaggarwl who is tracking this.

Hey @StefH Thanks for more feedback ;) We're moving forward with this page and will be maintaining this page as the sole information for the DotNetCLI task. Thanks again and have a great day!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

cijujoseph picture cijujoseph  Â·  3Comments

Naphier picture Naphier  Â·  3Comments

michhar picture michhar  Â·  3Comments

LennartAJansson picture LennartAJansson  Â·  3Comments

adnanebrahimi picture adnanebrahimi  Â·  3Comments