In this article, you will learn about a new system called NConsoler that I designed based on metadata.
Introduction
Usually, parsing arguments in console applications takes a lot of time. You can find a few solutions on the Internet that make it easier to implement this task, however, they are not very simple and flexible. Therefore, I decided to design a new system based on metadata and call it NConsoler
.
Using the Code
The main idea is to find a way to transform a set of arguments to call a particular method. In case the arguments are wrong, the application must return a human understandable error message, with error details, to provide user friendly behavior for the application. Also, it is easy to provide help information using the metainfo.
Well, to get the required method with a set of arguments, the method should be marked. For this functionality, we could use attributes that ideally suit this job. I implemented an Action
attribute:
[Action]
public static void Method(...)...
Also, methods could have required and optional arguments to add flexibility in the development process. This could be realized by including attributes as well as using the Action
attribute for a method:
[Action]
public static void Method(
[Required] string name,
[Optional(true)] bool flag)...
As far as we know, Method
must take a set of input parameters, and for optional parameters, we have to set optional values, by default.
The last thing to do before running the application is to design a Main
method:
public static void Main(params string[] args) {
Consolery.Run(typeof(Program), args);
}
The type that has a method marked as Action
should be passed into the Run
method and the arguments must be passed as well.
The complete source code is available here:
using System;
using NConsoler;
public class Program {
public static void Main(params string[] args) {
Consolery.Run(typeof(Program), args);
}
[Action]
public static void Method(
[Required] string name,
[Optional(true)] bool flag) {
Console.WriteLine('name: {0}, flag: {1}', name, flag);
}
}
Let’s run our application:
> program.exe Max /flag
name: Max, flag: true
And now, with the inversed flag:
> program.exe Max /-flag
name: Max, flag: false
Certainly, in the definition of the Action
method, the user could make a mistake, and in most libraries, the source of the error is not obvious; therefore, an adequate error message is extremely important. I pointed this out at the beginning of the article. Before starting an action method, NConsoler
checks meta-information as well as the parameters of the command line and displays a detailed error message with the eventual cause of error. This is a continuation of the “Design by contract” strategy.
More information can be found on the NConsoler site.
History
- 8th September, 2008: Initial version