Windows Form Designer Custom Control changes Anchor which works correctly at run-time, but not at design-time?

You are hardcoding the property value. So assign the value in the constructor, make it non-browsable so it won't show up in the properties window and ensure that the value cannot be changed and doesn't get serialized. Like this.

You are hardcoding the property value. So assign the value in the constructor, make it non-browsable so it won't show up in the properties window and ensure that the value cannot be changed and doesn't get serialized. Like this: ref class MyControl : Control { public: MyControl() { __super::Anchor = AnchorStyles::Top | AnchorStyles::Left | AnchorStyles::Right; } Browsable(false), EditorBrowsable(EditorBrowsableState::Never) DesignerSerializationVisibility(DesignerSerializationVisibility::dden) virtual property System::Windows::Forms::AnchorStyles Anchor { AnchorStyles get() override { return __super::Anchor; } void set(AnchorStyles) override { // do nothing } } }.

Yet again, you are spot on. If my reputation allowed it, I'd be giving you a vote. – bobinski Feb 9 '11 at 1:18.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.