Inspection for (mis)usage of module fields backed by property

[bclothier]

Given this code:

Private BackingField As String

Public Property Get Field() As String
  Field = BackingField
End Property

Public Property Let(NewValue As String)
  'Some complicated logic goes here...
  BackingField = NewValue
End Property

Public Sub Doh()
  BackingField = "Bypassing the logic!"
End Sub

It's too easy to wrongly reference the backing field within the module; there are instances where bypassing the logic embedded in the setter is fine, but I think it'd be good to have an inspection to bring attention of this possible oversight, so an explicit choice can be made whether it's intended to bypass the setter's logic or not. Given this isn't an error per se, the inspection would be a suggestion, or warning.

This also implies a need for the @IgnoreOnce annotation with a comment to make it clear we are deliberately assigning to the backing field.

[Hosch250]

Brilliant idea. The IgnoreOnce attribute should automatically work, but it would be something we need to test.