Inspection for shadowed/duplicated member attributes

[ThunderFrame]

It's possible to have a VB_Description defined for the Get, Set and Let of a Property, and VBE doesn't enforce consistency (it only recognizes the first VB_Description encountered). It may be that it is possible to have multiple descriptions, but the VBE's Object Browser displays a Property as a single member (regardless of whether it is implemented as Get, Let and/or Set).

RD should ensure that only one VB_Description is defined per Property. It may well be appropriate to have different help contexts and/or shortcut keys per property.

[retailcoder]

I think IllegalAnnotationInspection should be tweaked to pick these up, so we can report the problem before the attribute is even added to the member. Then yeah, there's still a need to report actual conflicting member attributes, on property members.