Unordered parameters

[GoogleCodeExporter]

What steps will reproduce the problem?


What is the expected output? What do you see instead?

Currently, with required params, you have to put the param value in the 
necessary order to map it in to the correct parameter. 

Most windows systems administrators are used to specifying switches, like, 
/paramName or -paramName, without regard to order. 

Would you be willing to make nconsoler more flexible, allowing a programmer 
using nconsoler to configure it such that we can have required params that must 
be in order as it is now, but also required params where the switch is required 
and order is not relevant?

What version of the product are you using? On what operating system?

2.0

Please provide any additional information below.

Original issue reported on code.google.com by [email protected] on 2 Sep 2011 at 5:50

[GoogleCodeExporter]

Sorry, this is not a defect, it's a question. I clicked save before I realized 
the type. 

Original comment by [email protected] on 2 Sep 2011 at 6:19

[GoogleCodeExporter]

Nice suggestion, we will add this feature to the backlog

Original comment by [email protected] on 2 Sep 2011 at 11:25

[GoogleCodeExporter]

Original comment by [email protected] on 2 Sep 2011 at 11:26

• Added labels: Milestone-Backlog

[GoogleCodeExporter]

This seems related:
http://code.google.com/p/nconsoler/issues/detail?id=7

Original comment by [email protected] on 14 Jan 2012 at 5:54