Visual studio does not gray out properties with a ReadOnlyAttribute(true)

Question

I know it's stupid but visual studio (2010) doesn't gray out my properties tagged with ReadOnlyAttribute, I can't edit their values (if I try to do it, simply return to the previous value), but they aren't grayed out, I think it's really boring this when using the editor

Is there an option or an attribute that I'm forgetting?

Thanks for any help

Example 1:

    /// <summary>
    /// Inform if the LcdDisplay has been already initiated
    /// </summary>
    [Description("Inform if the LcdDisplay has been already initiated")]
    [DefaultValue(false)]
    [ReadOnly(true)]
    public bool Initialized { get; private set; }

Initialized is not grayed out

Pretty sure this is a bug. One that just never gets put to the test, no point in showing a non-editable item in the grid. — Hans Passant, Jan 05 '11 at 06:20
I removed those properties but well it's a bit uglier (and readonly attribute it's useless if not used in this way!), thanks by the way — Francesco Belladonna, Jan 06 '11 at 04:01

score 0 · Answer 1 · answered Jan 04 '11 at 23:39

0

This behavior is by design.

To make the property grayed out, remove the setter. (or make it private)

If you only want it to be readonly at designtime, you can make a separate writable property and add [Browsable(false)] to hide it from the property grid.

answered Jan 04 '11 at 23:39

SLaks

868,454
176
1,908
1,964

1

It's strange because the setter IS private – Francesco Belladonna Jan 04 '11 at 23:48

score 0 · Accepted Answer · answered Jul 21 '11 at 09:11

0

The only way to have this behaviour is not to have a setter, maybe because the designer see the private field as something that he can access to so it doesn't gray out it.

answered Jul 21 '11 at 09:11

Francesco Belladonna

11,361
12
77
147

Visual studio does not gray out properties with a ReadOnlyAttribute(true)

2 Answers2