|
Hello Experts,
one of the console applications I wrote is about to get modified to do a similar job to the one it was first designed to do.
Its command-line parameters parsing works. But I never have been really happy with it. This example
tool.exe SetDo FirstLed On should make an attached device switch its first LED on, obvisously. And it does so.
What bothers me is that SetDo has to be the first parameter, FirstLed the second and On the third. No way for the user to put an option before SetDo.
Since the modifications will change the possible actions anyway, I thought of finding a more standard library instead of using my own parsing.
First I checked the GNU getopt .NET port[^] and found using it horrible. You have to specify a format string, only for one-character options and a switch statement that matches the format string. Then you can attach long options that use a short option to determine what action they trigger.
That approach appears to be inspired by sprintf's format string[^], which we all know about and that it works. It just is so unintuitive to use from a programmer's point of view.
My second try was Mono.Options[^]. It doesn't require a format string. You just have to fill a generic list with one object per supported command. Short and long option names are supported in the object's constructor, along with a description of the command (for the auto-generated help screen) and a method to call during runtime.
Now I recognize that there's still a lot of work to do by hand since not all my options are boolean switches. The example I gave above uses two enumerations, one that holds all possible digital outputs to manipulate, the other for the state that should be the result of the manipulation. It doesn't look like there is an easy way to get that into the auto-generated help file, nor that the parser can handle situations like "Option A must preceed one of enum B's values followed by enum C's values", does it?
Does anyone know of a command-parsing library suitable for that?
Or should I rather tweak the working one into having my options position-independent?
Ciao,
luker
|
|
|
|
|
|
No other responses?
Having given it some more thought... If I understand you correctly, you are using Enumerations for each parameter. Why not put them all in one enumeration?
|
|
|
|
|
Why? You covered it with that huge pile of links to various libraries!
|
|
|
|
|
I'd still prefer to see some discussion.
|
|
|
|
|
OK, cool. I'd layout the command line format like this, following the old DOS spec of everything inside square brackets being optional:
tool.exe [[/option] [value]] [/cmd "targetNoun actionVerb value"]
That would make it easier to parse as each switch is either a "Named Switch" or a "Named Value".
The CMD switch could even be extended like this:
/cmd "targetNoun actionVerb [value][;...]"
making it easier to parse for multiple commands to execute in the specified order.
|
|
|
|
|
I was thinking...
TOOL action /LED=n|(list) /STATE=ON|OFF
e.g.
TOOL SET /LED=1 /STATE=ON
TOOL SET /LED=(3,5,7) /STATE=OFF
(But what other actions are there?)
Or
TOOL /ON=n|(list) | /OFF=n|(list) ...
e.g.
TOOL /ON=1 /OFF=(3,5,7) /ON=2
|
|
|
|
|
Yeah, we have no idea what else he's got to control, nor how he has to refer to them. The LED=n might work for him but it really depends on the complete list of items he needs to control and the verb and value options available for each of those. When he knows that, then he might be able structure a standard format command line if there are a lot of possibilities or, if not, simplify it to what you've said.
|
|
|
|
|
I want Import 3D model in C# windows from aplication,
and rotating it.
Would you Help me, Please!
|
|
|
|
|
Where are you stuck? What have you tried, what failed and why?
Until we know where you need help you can't expect us to be able to offer any!
|
|
|
|
|
Sure[^]. Knock yourself out.
|
|
|
|
|
Exactly What? you can search about WPF 3D Modeling in C#.
Good answers wait for you! 
/* LIFE RUNS ON CODE */
|
|
|
|
|
Hello,
I've noticed that when I tried to set a string variable to the folderBrowserDialog.SelectedPath property it does not work. Can someone please explain why that is and is there a way around this? I don't want to have to keep writing folderBrowserDialog.SelectedPath every time I need to use it. Thanks in advance for your reply.
|
|
|
|
|
|
The "SelectedPath" property is already a string. See MSDN 
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
|
|
|
|
|
You're a "Senior Software Developer" and you're still making the noob mistake of calling ToString() on a string? 
|
|
|
|
|
ASPnoob wrote: I've noticed that when I tried to set a string variable to the folderBrowserDialog.SelectedPath property it does not work.
"Works on my machine".
Perhaps it'd help if you posted your code? The only way the property (which is a string, an can be assigned to a string-variable) is when the object that owns the property is not yet created. You'd get a refernce-exception.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
If the path you put in the SelectedPath property doesn't exist or is not a path under the path specified by the RootFolder value, it "won't work".
|
|
|
|
|
Thank you all for replying. The following is my code for creating a text file in a folder after browsing to it:
string myFolderPath = folderBrowserDialog1.SelectedPath;
string myFileName = txtFileName.Text.ToString();
if (folderBrowserDialog1.ShowDialog() == System.Windows.Forms.DialogResult.OK)
{
TextWriter myWriter = File.CreateText(myFolderPath + @"\" + myFileName + ".txt");
myWriter.Write("Hello World");
myWriter.Close();
}
The "UnauthorizedAccessException was unhandled" exception was thrown and I get the error message "Access to the path 'C:\MyTestFile' is denied" when I run the code above. It works fine if I use folderBrowserDialog1.SelectedPath in place of myFolderPath.
|
|
|
|
|
You can't set string myFolderPath = folderBrowserDialog1.SelectedPath; until after the dialog has returned!
The string there before the call is not modified in place by the dialog.
It is replaced by the dialog.
myFolderPath just has the wrong value.
|
|
|
|
|
Without seeing the result of the string concatentation you're using inside the parenthsis in the CreateText call, it's impossible to say for sure.
But, if the result is actually a valid path and you're trying to create a file in the root of C: on Vista or Win7, you'll get that error because normal Users cannot create files in the root of C:. You can make folder, not files.
On top of that, why are you calling ToString() on txtFileName.Text?? The .Text property returns a string, so the call to ToString() is a bit redundant.
modified 8-Feb-13 15:47pm.
|
|
|
|
|
Thank you everyone for responding. After reading your posts and reexamining my code, I realized that I did make two noob's mistakes. I've fixed the errors and everything works fine. I learned some valuable lessons today and that was the intention of the current project I'm working on. Thanks again for replying.
|
|
|
|
|
Hi,
How can i data transfer from android mobile phone to .NET application?
|
|
|
|
|
Don't repost like this. People won't help if you do.
|
|
|
|
|
Hi, İ want to data transfer from android mobile phone to .NET application. How can i do? or how can find source code?
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
