I'm not sure how to organise the properties in theInitializeComponent of the disigner code. I have one property that relies on two other properties, however they come after the dependant property alphabetically. I've tried using theISupportInitialize with begin Init and End init, but I'm not really sure that is the solution I'm looking for. Also how does that relate to the order of initialising the properties once they've been set?

Any help (code samples are greatly appreciated) will be welcomed :)

Validate only during and afterISupportInitialize.EndInit is called.

---

MSMVP VC++

Properties and implementations are different. You can Implement ISupportInitialize in such as way that it applies property changes made by the designer in EndInit, in any order you choose.

---

MSMVP VC++

Hi, thanks for the reply, but I'm afraid it still doesn't make sense to me. I have propertCheck,Minimum andMaximum. all type int

if I have the following scenario then I'll get an error when running a form with my control because minimum and maximum would still have the value 0 when Check is initialized.

How do I circumvent this problem usingISupportInitialize?

private int iCheck;
private int iMinimum;
private int iMaximum;

public intCheck
{
get
{
returniCheck;
}
set
{
if(value <iMinimum
|| value > iMaximum)
{
throw new ArgumentException("Check must be between Minimum and Maximum");
}
}
}

public intMinimum
{
get
{
returniMinimum;
}
set
{
iMinimum = value;
}
}

public intMaximum
{
get
{
returniMaximum;
}
set
{
iMaximum = value;
}
}

Validate only during and afterISupportInitialize.EndInit is called.

---

MSMVP VC++

Hi,

As Sheng Jiang said, we can use Implement ISupportInitialize.

Best regards,

Ling Wang

---

Please remember to click “Mark as Answer�on the post that helps you, and to click “Unmark as Answer�if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.