Add ability to require arguments by group about powerargs

[workabyte]

i believe the issue found here #47
may solve for what you are looking to do. With the example you provided you would want to do something like

public class SampleArgs
{
[ArgCantBeCombinedWith("B")]
public bool A { get; set; }
[ArgCantBeCombinedWith("A")]
public bool B { get; set; }
[ArgCantBeCombinedWith("D")]
public bool C { get; set; }
[ArgCantBeCombinedWith("C")]
public bool D { get; set; }
}

if you read through the reply provided by the creator of this project you should be able to accomplish most of what you are looking for with that feature out of the box.

Hope this helps

[adamabdelhamed]

@PCkris, thanks for writing that up. You're exactly right. @jehrenzweig, what you're asking for has been done, for example in PowerShell, but I think it's difficult for users to understand sets of required parameters (called parameter sets in PowerShell), but it's easy to understand that a particular argument can or can't be combined with another.

If you read through #47 then you'll also see that there's the if and ifnot enhancements that have been added to [ArgRequired] that give you all the flexibility you should need.