Code inspection: Unassigned field (non-private accessibility)
This inspection reports public fields that are used in some operations or returned by a method, but are never assigned a value. This often indicates that some part of your code is not functioning as intended, or that the field is redundant and should be removed, or that the field should be initialized from a constructor .
For the solution-wide inspection to work, you need to enable at least one of the following:
Simplified global usage checking: select Show unused non-private type members when solution-wide analysis is off on the page of ReSharper options Alt+R, O.
Solution-wide analysis: select Enable solution-wide analysis on the page of ReSharper options Alt+R, O.
Note that even if the reported field has no direct usages in your solution, there could be cases where it is used indirectly — for example, via reflection — or it could just be designed as public API. In all those cases, you would want to suppress the usage-checking inspection for the field in one of the following ways:
The recommended way is to decorate the implicitly used field with a code annotation attribute. There are two attributes for this purpose: [UsedImplicitly] and [PublicAPI], which are functionally similar, but let you and your teammates understand how the field is actually used.
You can also suppress usage-checking inspections with any custom attribute. To do so, mark the definition of that attribute with the [MeansImplicitUse] attribute.
And finally, you can suppress a specific usage-checking inspection as any other code inspection with a suppression comment or a suppression attribute.