Project status: maintenance mode

[natemcmaster]

This project is now in maintenance mode. 4.0 is the last release I intend to make.

Thank you to the dozens of contributors over the years. I believe the work we have done here has produced a highly stable and usable API for building most command line apps.

What does 'maintenance mode' mean?

• I will only work on the most critical of bugs will be fixed (such as security issues). If you have other small patches, feel free to send a pull request. Patch = no new functionality and no breaking changes.
• No new features will be added. If you really, really (like really truly) want to build new features, reach out first before starting work. We can discuss good ways to extend this library and help you avoid throw-away work.
• I won't be regularly reviewing open issues. Most issues will timeout and auto-close after 1 year..
• I have decided to stop working on this project, but have not put this into "archive mode" on GitHub. Contributors are still welcome to help out by answering others' questions in the issues forum.

If you need help with this project, please ...

• read the documentation (https://natemcmaster.github.io/CommandLineUtils/),
• look at the samples (https://github.com/natemcmaster/CommandLineUtils/tree/main/docs/samples),
• review existing questions (many were answered already) (https://github.com/natemcmaster/CommandLineUtils/issues?q=label%3Aquestion+),
• or use a programming Q&A forum such as StackOverflow.com

Feel free to add comments/questions below. And, thanks again to all the contributors for your work over the years!
-Nate

[LordMike]

@natemcmaster you should update the Readme. At the bottom it says the following:

This fork, on the other hand, will continue to make improvements, release updates, and accept contributions

Since the project is not abandoned, I don't necessarily think it should be written in the description of the repo/nuget packages, but you could consider stating this there too :).

Thanks for all the effort on the project, it's been very helpful in all our other projects :)

[natemcmaster]

Good suggestion. Updated the readme in #488

[thohng]

New library coming System.CommandLine, another options for developers.

History: https://github.com/dotnet/command-line-api/blob/f2556cacb35c0b68201d73eaf1c0df8c5e57e43e/docs/History.md

https://www.nuget.org/packages/System.CommandLine

https://learn.microsoft.com/en-us/dotnet/standard/commandline/

[attilah]

@thohng yeah it did not age well :-) ....it is still coming and Microsoft does not provide a builtin way to work with command line arguments...

DotNet.CommandLine.CLI is archived all tools should have moved to System.CommandLine by now, EF 8.0 still using this archived library...

Wondering what will happen in this space!

[bleepzter]

.NET's System.CommandLine has a really messed up way of integrating with IHostBuilder and IHost. Its like an afterthought.
This library has a much better way of running the command without interfering with DI and the IHostBuilder. Please don't give up on this library because the other one is immature IMHO.

[FrankRay78]

Re: 'CommandLine', I contribute to Spectre.Console and I've heard some internal Microsoft teams actually use that, instead of their own 😉