Please see my comment about VB.NET vs C#. Here is the good news: you can easily and automatically translate one into another with 100% accuracy. There are on-line and off-line/stand-along solutions, so, first of all, pay attention for the open-source stand-along tool, ILSpy, which can easily translate the whole project from C# to VB.NET and back. Please see my past answers:
Code Interpretation, C# to VB.NET[
^].
Now, armed with all that, you can easily use C# projects as well. First, you can simply build available projects, references the assembly in your VB.NET project and just use in exact same was as it was in VB.NET. In this approach, you simply won't see any difference. And you also can translate, it you need it for better understanding.
That said, not you can use my work on command-line parameters, which is extremely easy to use (and one more, more complicated, is recommended in my article):
Enumeration-based Command Line Utility[
^].
Good luck,
—SA