ReSharper 2020.1 Help

Code Inspection: Auto-property can be made get-only (non-private accessibility)

Starting from C# 6.0, you can define get-only auto-properties, which (similarly to readonly fields) can be only initialized via a constructor or an initializer. ReSharper detects and helps you remove the redundant set accessor on auto-properties that are initialized from the constructor/initializer and have no write usages.

In the example below, an immutable class is intended, and once the value for the Name property is checked for nullability in the constructor, it can be safely used without further null checks. However, the private setter does not guarantee that the property will not be changed later in private members. Therefore, it is a good idea to make this property get-only to prevent any modifications.

public class Person { public string Name { get; set; } // Auto-property can be made get-only public Person(string name) { Name = name ?? throw new ArgumentNullException(nameof(name)); } public override string ToString() { return $"NAME: {Name.ToUpper()}"; } }

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: 08 May 2020