Skip to main content

Digging through SignalR - Command Line Arguments

SignalR contains a console application that can be used to make stress tests. The solution that was used to parse the command parameters was ‘cmdline – Command Line Parser’. This is a pretty nice library that can be installed using NuGet. This command line parses works perfectly, this is why the last time when it was updated in in September 2012.
Beside this solution, you can find another solution on Codeplex and github called very similar “Command Line Parser Library”. Both solutions are great and resolve the same problem in a very similar way. First time when I saw this two solutions I could swear that are the same solution (from the available API).
I saw a lot of projects, where people started to implement their own arguments parsers, even if we have plenty of them on the marker. It is not so important what command line parser you use it, as long you use it and don’t rewrite it again and again. In general, the use cases that we need to support are pretty simple and are covered by almost all the current solutions.

Because I prefer Command Line Parser library, I will present this one. I’m a fan of it because this stack is available from 2009 and it is still updated and maintained. This is a key feature of any framework.
When you are using this stack you have the possibility to declare a class that will represent the parameters that are send by the user to you. Each input argument from the console application can be mapped to a property of the class. In this way, it will be pretty easily to check what arguments were introduce by the user, what is the value and so on.
This mapping between input arguments and your class property is made through attributes. There is a base attribute called ‘Option’ that is used in most common cases. For each attribute you have the ability to set a normal name of the option and also a short name. For example you can have an argument that has the full name ‘help’ and a short name called ‘?’ (for power user).
protected class MyFooOptions
{
  [Option("c", "copy", Required = true, HelpText = "Copy file.")]
  public bool Copy { get; set; }

  [Option("d", "delete", DefaultValue = false, HelpText = "Delete file.")]
  public bool Delete { get; set; };

  [Option(null, "input", HelpText = "Location of input file.")]
  public string InputFilePath { get; set; };
}
For each argument we have the ability to specify if the argument is optionality or required. When we set the ‘HelpText’ property we will have the ability to generate automatically the help legend for all arguments without needing to format it and so on. The only thing that we need to do is to use ‘HelpText’ class that can render automatically our help messages pretty nice.
[HelpOption]
public string GetHelp()
{
    HelpText help = new HelpText {
        Heading = new HeadingInfo("<>", "<>"),
        AdditionalNewLineAfterOption = true,
        AddDashesToOption = true };
    help.AddPreOptionsLine("<>");

    // Add our options.
    help.AddOptions(this);
    return help;
  }
To be able to parse the input arguments and map them to our class we need to call the following method:
MyFooOptions myOpt = new MyFooOptions();
ICommandLineParser parser = new CommandLineParser();
parser.ParseArguments(args, myOpt)
Magic.
Other features are supported like having a list of items for a specific option or specify a method that will be used when the user wants to access the help.
protected class MyFooOptions
{
  [Option("c", "copy", Required = true, HelpText = "Copy file.")]
  public bool Copy { get; set; }

  [Option("d", "delete", DefaultValue = false, HelpText = "Delete file.")]
  public bool Delete { get; set; };

  [Option(null, "input", HelpText = "Location of input file.")]
  public string InputFilePath { get; set; };

  [OptionList("inputlist", "inputlist", Separator = ',', HelpText = "List of files.")]
  public IList<string> InputList { get; set; };
}
The last thing that I like to this solution is ‘ValueListAttribute’. This attribute is useful when user start to enter or use arguments that are not mapped. In this case, we can have a property of type lList<string> where all this arguments will be added. We can process this list if we want or we can ignore it.
protected class MyFooOptions
{
  [Option("c", "copy", Required = true, HelpText = "Copy file.")]
  public bool Copy { get; set; }

  [Option("d", "delete", DefaultValue = false, HelpText = "Delete file.")]
  public bool Delete { get; set; };

  [Option(null, "input", HelpText = "Location of input file.")]
  public string InputFilePath { get; set; };

  [OptionList("inputlist", "inputlist", Separator = ',', HelpText = "List of files.")]
  public IList<string> InputList { get; set; };

  [ValueList(typeof(List<string>), MaximumElements = 10)]
  public IList<string> Items { get; set; };
}
Cases like missing required options are already managed by this solution. Of course you can set custom behavior to it.

Enjoy!

Comments

Popular posts from this blog

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

Run native .NET application in Docker (.NET Framework 4.6.2)

Scope
The main scope of this post is to see how we can run a legacy application written in .NET Framework in Docker.

Context
First of all, let’s define what is a legacy application in our context. By a legacy application we understand an application that runs .NET Framework 3.5 or higher in a production environment where we don’t have any more the people or documentation that would help us to understand what is happening behind the scene.
In this scenarios, you might want to migrate the current solution from a standard environment to Docker. There are many advantages for such a migration, like:

Continuous DeploymentTestingIsolationSecurity at container levelVersioning ControlEnvironment Standardization
Until now, we didn’t had the possibility to run a .NET application in Docker. With .NET Core, there was support for .NET Core in Docker, but migration from a full .NET framework to .NET Core can be costly and even impossible. Not only because of lack of features, but also because once you…