DotNetCoreCLI commands are inconsistent

[weshaggard]

The DotNETCoreCLI task supports various commands however they all seem to be inconsistent. A couple examples:

arguments: While the task supports an optional arguments parameter it doesn't get used by all the tasks. I was trying to pass additional augments to the pack command and while the YAML accepts it the pack command completely ignores it.

Another example is the verbosity parameter some if you check out the documentation you see "verbosity" listed twice in the doc table and in the same command you see it listed at verbosityRestore and verbosityPack. Is there really any reason that all the commands cannot simply use verbosity as it is a common option for all.

Please work on cleaning up this task to make the different commands consistent and only add additional parameters for things that are truly unique for the given command. At this point to workaround these I will need to stop using the DotNETCoreCLI task and make the call directly with a script.

[issacnitin]

@weshaggard Thank you for the feedback, I agree the commands are inconsistent right now and need cleanup. We'll start working on this as soon as possible.

[OliverRC]

I agree, pack should allow arguments to be passed.

[smileyiori]

Even if you pass the arguments, the CLI does not execute them.
In my case I set nobuild: true

and my command looks like:

But the project still building. Is there something related?

[dmcweeney]

Just some feedback here - this is painful for me at the moment - after introducing second repo into the build script all the dotnet commands are failing - trying to use the workingDirectory property to fix it but its not supported by some of the dotnet commands and the docs dont clarify

[bishal-pdMSFT]

Cc @tejasd1990 @pulkitaggarwl

[sayedsaad07]

Any updates on this issue please
I tried different combinations but nothing seems to work
Working-directory is ignored
even below does not work
dotnet restore ${{github.workspace}}/webapi

[github-actions]

This issue is stale because it has been open for 180 days with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days

[dmcweeney]

Hi @bishal-pdMSFT any update on this?

[github-actions]

This issue is stale because it has been open for 180 days with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days