User control (ascx) and properties

asp.net properties user-controls viewstate
Jagd picture Jagd · Jul 24, 2009 · Viewed 10.7k times · Source

The only way I've found to persist property values within a user control is to use the ViewState.

public string Title {
        get { return Convert.ToString(ViewState["Title"]); }
        set { ViewState["Title"] = value; }
    }

I can't say I'm real impressed with this though, as the more properties a user control has the more crap you'll be sticking in the ViewState. Is there a better way to persist properties?

Answer

Sayed Ibrahim Hashimi picture Sayed Ibrahim Hashimi · Jul 24, 2009

It depends. If you need to property values to be persisted beyond a post-back then you'll either have to use ViewState or Session. Since those controls are re-created on each post back you can't really maintain that state otherwise.

Related questions

appSettings vs applicationSettings. appSettings outdated?

I've got some questions about two ways to save settings in the web.config. Appsettings: Look in web.config <appSettings> <add key="key1" value="value1"/> <add key="key2" value="value2"/> </appSettings> Usage …

Read More
Accessing masterpage properties from child pages in ASP.net VB

I have masterpage.master.vb where I have properties, such as; Private _SQLerror As String Public Property SQLerror() As String Get Return _SQLerror End Get Set(ByVal value As String) _SQLerror = String.Empty End Set End Property Then I have …

Read More
Why should I use a private variable in a property accessor?

Sorry If I am being noob, I have this doubt, why do we use private variables and set them using properties ? Why can't we just use properites alone ? I am talking about situations like this private string _testVariable; public string …

Read More