
June 10th, 2002, 05:05 AM
|
|
Contributing User
|
|
Join Date: Dec 2002
Posts: 14,575
  
Time spent in forums: < 1 sec
Reputation Power: 23
|
|
|
Persisting properties in components and controls?
<i><b>Originally posted by : Yevgeny (batman@panasonic-engineering.ru)</b></i><br />In System.Web.UI.Control and all derived classes all properties must be persisted with attributes or inner properties in .aspx file where control is placed. <br /><br />In winforms we can simply edit poperties of control in design-time mode and they are serialized to resources and when application is starting they are deserializing. Visual Studio adds some code to codebehind of the page to provide this. <br /><br />We can also drop to aspx page not controls but components from toolbox of VS.NET and see that their properties are also desirializing from resources or initializing in other way by our aspx Page. <br /><br />What must I do to make properties of my control to initialize from resources in my codebehind source code like all Component inheritors do instead of placing this properties to persist in aspx file? Even I don't need my properties to persist through page roundtrips and dont't need to place anything to ViewState.<br />
|