InfoQ - .NET 4 Will Not Have a Command Line Parser
“…
We are not shipping System.Shell.CommandLine in .NET 4. This was based on an intern project from a couple of years back that was mistakenly public in the .NET Framework 4.0 CTP. It wasn't a design that we were happy with and has been removed and will not be present in the next preview release.
We have a *much better* command line parsing API, along the lines of Mono.Options, that we're planning to release on CodePlex later this year.
…”
This made me laugh (as one developer to another, as one who has made mistakes and am laughing with, not at, the team)… Doh!
You can almost hear the chatter from Microsoft, “Hey what’s this Command Line API in 4 that Miguel is jumping up and down about?”
“What command line API? There’s no Command line API in 4”
“Um… Yeah, there is… Right here…”
“Oh Crap! That’s So and So’s project, what the heck is THAT doing there?”
“You mean it’s not supposed to be there?”
“NO!”
“Oh”
Related Past Post XRef:
Command Line Parsing – A wheel we can finally stop reinventing with .Net 4.0
No comments:
Post a Comment
NOTE: Anonymous Commenting has been turned off for a while... The comment spammers are just killing me...
ALL comments are moderated. I will review every comment before it will appear on the blog.
Your comment WILL NOT APPEAR UNTIL I approve it. This may take some hours...
I reserve, and will use, the right to not approve ANY comment for ANY reason. I will not usually, but if it's off topic, spam (or even close to spam-like), inflammatory, mean, etc, etc, well... then...
Please see my comment policy for more information if you are interested.
Thanks,
Greg
PS. I am proactively moderating comments. Your comment WILL NOT APPEAR UNTIL I approve it. This may take some hours...