Mutual exclusive option is not enforced (even when settings.MutuallyExclusive == true)

[jsmarsch]

I'm working with the stable build (1.9.71). I am trying to set up mutually exclusive options. I have set a mutual exclusion group, and given each option a different string. I also set the MutuallyExclusive option in the parser settings to true.

But, when I call parser.ParseArgumentsStrict(), it always returns true -- even if I specified the mutually exclusive options in the command line.

Is this a known bug?

[nemec]

Can you post a sample of the classes/command line you're using? There has been confusion in the past on how the mutually exclusive option works, you may be seeing those issues.

[jsmarsch]

Sure.
I'm using verbs, so here is some content from one of my suboptions that uses mutual exclusion:

[Option('t', "tableName", HelpText = "Only the named table (schema.tablename) will be enabled for Cdc", MutuallyExclusiveSet = "singleTable")]
public string TableName { get; set; }

[Option('a', "all", MutuallyExclusiveSet = "alltables", HelpText = "All untracked tables will be enabled for cdc, except for tables named in audit.CdcExclusion table.")]
public bool AllTables { get; set; }

The intent is that you cannot specify myApp myVerb -a and myApp myVerb -t in the same execution.

Here's where I set up the parser:

            var commandLineParser = new Parser(s =>
            {
                s.HelpWriter = Console.Error;
                s.IgnoreUnknownArguments = false;
                s.MutuallyExclusive = true; 
            });
            try
            {

                if (!commandLineParser.ParseArgumentsStrict(args, options,
                    (v, i) =>
                    {
                        verb = v;
                        verbInstance = i;
                    }))
                {
                    Environment.Exit(Parser.DefaultExitCodeFail);
                }

[nemec]

Try adding them both to the same set instead. This SO post implies that the wiki for 1.x is totally wrong and that the new 2.x beta has fixed the issue.