Is read-only auto-implemented property possible?
Solution 1:
The answer below was written back in 2010. In C# 6 (released in 2015) you can write read-only automatically-implemented properties:
// This can only be assigned to in a constructor
public int Foo { get; }
You're absolutely right. Properly read-only automatically implemented properties are currently impossible. Making the setter private isn't the same thing, regardless of what some books and MSDN might say :)
If I ruled the world, this would not be the case. When I see some of the language designers at NDC 2010 in June (please come along!) I intend to try to persuade, bribe, cajole and generally make a nuisance of myself until they agree. It's just one wafer-thin feature, after all.
Looking at that MSDN article, the text itself doesn't say that it creates a read-only automatic property. It creates an immutable type using an automatic property, and that's correct. The only problematic bits are the comments saying
// Read-only properties.
... which are definitely wrong. The framework agrees with us:
var prop = typeof(Contact).GetProperty("Name");
Console.WriteLine(prop.CanWrite); // Prints True
Solution 2:
The property is read-only outside the Foo class. I think that's what article is getting at.
But it's not the same as marking a variable with the readonly keyword.
Solution 3:
It's confusing. You should differentiate read-only to the c# readonly (what the keyword means).
- read-only: they mean that no one outside can write to it directly, only read.
- C#
readonly: you can only write to it in the constructor, then never more.
Solution 4:
No, it's not possible to make an auto-implemented property readonly. For the page you linked:
with auto-implemented properties, both a get and set accessor are required
A read-only property has NO set accessor.
A property without a set accessor is considered read-only
Solution 5:
Private set is not the same as readonly.
Similar to methods or fields, the private keyword makes the visibility of the setter available to only the class itself. Other objects cannot use the setter, but methods of the class itself can call it freely. Hence your test code compiles and works fine.
It appears to external objects as a readonly property, but it isn't read-only in the true definition.