Sarosh,

>>Do you have something that you can share with all of us there on UT?
e.g. A base class library with all the basic controls (TextBox, ComboBox etc) with the correct/required overrides etc.

Nope, afraid not. Some of our Framework classes are pretty complicated and I have never taken the time to make a simplified version for public consumption, other than in bits and pieces in answer to some posts here.

I can guarantee you that the company I work for would not like me posting our Framework classes, in their entirety, anywhere. <g>

~~Bonnie


>Hi!
>
>Do you have something that you can share with all of us there on UT?
>
>e.g. A base class library with all the basic controls (TextBox, ComboBox etc) with the correct/required overrides etc.
>
>Thanks
>
>Sarosh
>
>>
>>So, here's how you avoid that:
>>
>>

>>public class MyTextBox : System.Windows.Forms.TextBox
>>{
>>	public MyTextBox()
>>	{
>>		this.BackColor = Color.Firebrick; ;
>>	}
>>	[DefaultValue(typeof(System.Drawing.Color), "Firebrick")]
>>	public override System.Drawing.Color BackColor
>>	{
>>		get { return base.BackColor; }
>>		set { base.BackColor= value; }
>>	}
>>}
>>

>>With the DefaultValue attribute in place, when this TextBox is dropped on a design surface, the line of code:
>>
>>

>>this.BackColor = Color.FireBrick;
>>

>>
>>will *NOT* be generated. Without the DefaultValue attribute, it *WILL* be generated.
>>
>>~~Bonnie
>>
>>
>>
>>
>>
>>
>>>Hi Bonnie,
>>>
>>>>No, this particular problem that you had with the .Text property of a control is kind of special and that's because the IDE sets it when you drop the control on a design surface. You wouldn't normally handle it this way for other properties. Normally, all you need to do is set it in the constructor.
>>>
>>>I understand now. Thanks for the explanation.
>>>
>>>Alan