Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Stop producing Microsoft.Extensions.CommandLineUtils
This library was only intended for usage with ASP.NET Core's tools, and not a general purpose library. After receiving bugs and questions about this, we realized that we didn't really intend to produce and support a command-line parsing library. We will still leave the 1.0.0 and 1.1.0 versions of this library on NuGet.org, but the current plan is to stop producing new versions of this package. The source code is still available for internal use via Microsoft.Extensions.CommandLineUtils.Sources, however we will not be publishing this library again as a general purpose library.
- Loading branch information
2230370
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@natemcmaster Does the .NET core team have other recommendations for a command line utility?
2230370
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are probably half a dozen community libraries for parsing command-line args. Also, there may be full support from the BCL itself one day: https://github.com/dotnet/corefxlab/tree/master/src/System.CommandLine
By the way, here is more context on why we did this: #257 (comment)
2230370
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@natemcmaster whilst there are half a dozen other libraries for parsing command-line args, this was by far the best of them.
The corefxlab System.CommandLine one is probably the next best , however it isn't published to a main nuget feed.
2230370
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dennisroche glad you liked this library so much. The versions of this package on NuGet.org aren't going anywhere so you can still keep using those. However, we are not planning updates at the moment. Despite what you may think, we're actually a pretty small team. As @Eilon said in,
2230370
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FYI @dennisroche @ryanwalls as a replacement, I can recommend this: #261 (but this recommendation is not in an official capacity, of course.)