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.

Sign up for GitHub

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

Jump to bottom

dotnet-nuget-push fails: --config-file argument is invalid #50

Closed
dmccaffery opened this issue Mar 23, 2017 · 0 comments
Closed

dotnet-nuget-push fails: --config-file argument is invalid #50

dmccaffery opened this issue Mar 23, 2017 · 0 comments
Assignees
@dmccaffery
Labels
bug
Projects
condo
Milestone
2.0.0

Comments

@dmccaffery
Copy link
Member

A recent move to use dotnet-nuget-push directly rather than the NuGet xplat library in a custom task cannot work despite the documentation made available. The current CLI command does not support the --config-file argument even though it is in the examples.

We should move back to the custom task until this is resolved.

Related issue: dotnet/cli#6123
@dmccaffery dmccaffery added the bug label Mar 23, 2017
@dmccaffery dmccaffery added this to the 2.0.0 milestone Mar 23, 2017
@dmccaffery dmccaffery self-assigned this Mar 23, 2017
dmccaffery pushed a commit that referenced this issue Mar 23, 2017
@fritz-build
fix(nuget): resolve missing --config-path argument
a3e3c89 
* replace the `dotnet-nuget-push` command with the `PushNuGetPackage` custom task

Closes: #50
Related: dotnet/cli/#6123
dmccaffery pushed a commit that referenced this issue Mar 23, 2017
fix(nuget): resolve missing --config-path argument
02a9d8c 
* replace the `dotnet-nuget-push` command with the `PushNuGetPackage` custom task

Closes: #50
Related: dotnet/cli/#6123
@dmccaffery dmccaffery added this to Done in condo May 30, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dmccaffery dmccaffery

Labels
bug
Projects
No open projects
condo
Done
Milestone
2.0.0
Development

No branches or pull requests
1 participant
@dmccaffery