[HopelessDev]

Im reading pro c# 2010 by andrew troelsen and he said that automatic properties can't be buils as read only or write only

Quote

Unlike traditional C# properties, however, it is not possible to build read-only or write-only
automatic properties. While you might think you can just omit the get; or set; within your property
declaration as follows:
// Read-only property? Error!
public int MyReadOnlyProp { get; }

thats what he said. But how did System.Exception got away with it?

 public virtual string Message { get; }

This post has been edited by tlhIn`toq: 28 September 2012 - 02:40 PM

[CodingSup3rnatur@l-360]

It doesn't. The System.Exception.Message property isn't an automatic property. It's defined like this:

public virtual string Message
{
        get
        {
            if (this._message != null)
            {
                return this._message;
            }
            if (this._className == null)
            {
                this._className = this.GetClassName();
            }
            return string.Format(CultureInfo.CurrentCulture, Environment.GetResourceString("Exception_WasThrown"), new object[] { this._className });
        }
}

[HopelessDev]

I checked MSDN but that didn't show up. Thank you so much

Where did you get that? I tried typing "System.Exception.Message c#" in google but none of the result seemed right

[CodingSup3rnatur@l-360]

No problem. To get that code, I decompiled the System.Exception class using the standard version of .NET Reflector.

[Skydiver]

I usually do this to get the "readonly" effect:

class Person
{
    public DateTime BirthDate { get; private set; }
}

[Momerath]

If you think about it, not being able to make it read or write only makes sense. How would you set a read only property? What's the point of a write only property? Skydiver has the right solution, use the private keyword if you won't want outside code reading/writing the property.

This post has been edited by Momerath: 29 September 2012 - 10:59 AM