-
Notifications
You must be signed in to change notification settings - Fork 257
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.
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
[Feature]: Easier package publishing #11249
Comments
@chgill-MSFT Similar to the proposal you mentioned but it should also build in release mode and create package for you so you don't have to specify nupkg path yourself. If that's the plan then feel free to close the issue. I was even thinking to create a custom dotnet-tool for this exact purpose. This doesn't seem like a lot of work.
There should also be ability to set a default package source other than nuget.org but it's fine to just support nuget.org as it's the most commonly used. Ideally it should work just like cargo publish https://doc.rust-lang.org/cargo/reference/publishing.html |
Hi @bugproof! We recently started doing some more research around this area. I would love to know, what motivates you to push packages from your local machine using the CLI as opposed to the NuGet.org upload UI? cc @loic-sharma |
It's much faster. I don't have to visit NuGet.org just enter 1 short command and it's published. Much better experience. Instead of:
You just do:
|
NuGet Product(s) Involved
NuGet.exe, dotnet.exe
The Elevator Pitch
The command to publish packages to nuget.org could be simplified. In Rust's package manager - cargo you just do
cargo login apikey
(just one time) andcargo publish
and that's it.Similar nuget subcommand could do the following:
The api key could be saved in some json file or just use
nuget setapikey
Additional Context and Details
No response
The text was updated successfully, but these errors were encountered: