ReSharper 2021.1 Help

Code Inspection: Field can be made readonly (non-private accessibility)

This is a solution-wide code inspection. It only works when the Solution-Wide Analysis is enabled.

Say you have decided to make a Person class, initialized only via the constructor, but with publicly available fields. You go ahead and implement the following:

public class Person { public string Name; public int Age; public Person(string name, int age) { Name = name; Age = age; } public override string ToString() => $"Name: {Name}, Age: {Age}"; }
Public Class Person Public Name As String Public Age As Integer Public Sub New(name As String, age As Integer) Me.Name = name Me.Age = age End Sub Public Overrides Function ToString() As String Return String.Format("Name: {0}, Age: {1}", Name, Age) End Function End Class

If solution-wide inspection is enabled, ReSharper will detect that Name and Age fields are only being assigned in the constructor and offers to create an additional safeguard — by marking them readonly, we get to ensure that neither this class nor its users will inadvertently assign new values to these fields.

For the solution-wide inspection to work, you need either or both of the following:

  • The simplified global usage checking is enabled — Show unused non-private type members when solution-wide analysis is off on the Code Inspection | Settings page of ReSharper options(Alt+R, O).

  • The solution-wide analysis is enabled — Enable solution-wide analysis on the Code Inspection | Settings page of ReSharper options(Alt+R, O).

Note that even if a symbol has no direct usages in your solution and ReSharper warns you about it, there could be cases where symbols are used indirectly — for example, via reflection — or they could just be designed as public API. In all those cases you would want to suppress the usage-checking inspection for the symbol, and there are several ways to do so:

Last modified: 29 June 2021