B
breeve
From my testing ISupportInitialize is not honored in ASP.NET We have a
control like the following...
<ni:Meter ID="Meter1" runat="server" Range="67, 73" Value="70" >
</ni:Meter>
The Value property checks the range and throws an exception if the range is
outside its value. The default for the Range is 0-10. The trouble is when a
user saves the above mark up and closes the designer and reopens it, the
ASP.NET designer first tries to set the value to 70 before the range has been
set. The exception is thrown because the range is still its default value of
0-10. Interestingly, at run time the Range is set first so there is no issue.
It seems the evaluation of properties is inconsistant:
RunTime -> left to right
DesignTime -> right to left.
Is there anyway I can influence the ordering of properties or set them
together somehow?
control like the following...
<ni:Meter ID="Meter1" runat="server" Range="67, 73" Value="70" >
</ni:Meter>
The Value property checks the range and throws an exception if the range is
outside its value. The default for the Range is 0-10. The trouble is when a
user saves the above mark up and closes the designer and reopens it, the
ASP.NET designer first tries to set the value to 70 before the range has been
set. The exception is thrown because the range is still its default value of
0-10. Interestingly, at run time the Range is set first so there is no issue.
It seems the evaluation of properties is inconsistant:
RunTime -> left to right
DesignTime -> right to left.
Is there anyway I can influence the ordering of properties or set them
together somehow?