Home/ Questions/Q 622781
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T19:01:17+00:00

I recently read this article on smart use of ViewState and am particularly interested

  • 0

I recently read this article on smart use of ViewState and am particularly interested in not having unnecessary static data in ViewState. However, I’m also curious if I can do the same thing for a parent-child dropdown, like the classic Country/CountrySubDivision example.

So I have this markup:

    <asp:DropDownList runat="server" ID="ddlCountry" DataTextField="Name" DataValueField="ID" EnableViewState="false" />
    <asp:DropDownList runat="server" ID="ddlCountrySubdivision" DataTextField="Name" DataValueField="ID" EnableViewState="false" />
    <asp:Button runat="server" ID="btnTest" />

And this codebehind:

    public class Country
    {
        public string Name { get; set;}
        public int Id { get; set; }
    }

    public class CountrySubdivision
    {
        public string Name { get; set; }
        public int Id { get; set; }
        public int CountryId { get; set; }
    }

    protected override void OnInit(EventArgs e)
    {
        var l = new List<Country>();
        l.Add(new Country { Name = "A", Id = 1 });
        l.Add(new Country { Name = "B", Id = 2 });
        l.Add(new Country { Name = "C", Id = 3 });
        ddlCountry.DataSource = l;
        ddlCountry.DataBind();

        var l2 = new List<CountrySubdivision>();
        l2.Add(new CountrySubdivision { Name = "A1", Id = 1, CountryId = 1 }); 
        l2.Add(new CountrySubdivision { Name = "A2", Id = 2, CountryId = 1 });
        l2.Add(new CountrySubdivision { Name = "B1", Id = 4, CountryId = 2 });
        l2.Add(new CountrySubdivision { Name = "B2", Id = 5, CountryId = 2 });
        l2.Add(new CountrySubdivision { Name = "C1", Id = 7, CountryId = 3 });
        l2.Add(new CountrySubdivision { Name = "C2", Id = 8, CountryId = 3 });

        // this does not work: always comes out 1 regardless of what's actually selected
        var selectedCountryId = string.IsNullOrEmpty(ddlCountry.SelectedValue) ? 1 : Int32.Parse(ddlCountry.SelectedValue);

        // this does work: 
        var selectedCountryIdFromFormValues = Request.Form["ddlCountry"];

        ddlCountrySubdivision.DataSource = l2.Where(x => x.CountryId == selectedCountryId).ToList();
        ddlCountrySubdivision.DataBind();

        base.OnInit(e);
    }

So the first thing I noticed is that even when EnableViewstate is false, my country control’s value is persisted across requests with no extra effort. Sweet. That’s a lot of serialized stuff I don’t need to send across the wire on form submissions.

Then I came to the example above with a pair of parent-child drop downs, and I see that ddlCountry.SelectedValue is defaulting whereas Request.Form["ddlCountry"] is reflecting the control’s value.

Is there a way to keep EnableViewState = "false" without resorting to Request.Form to get a dependent control’s value?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Then I came to the example above with a pair of parent-child drop downs, and I see that ddlCountry.SelectedValue is defaulting whereas Request.Form[“ddlCountry”] is reflecting the control’s value.

    The reason you are seeing this behavior is that at that point in the page’s lifecycle, Viewstate hasn’t been loaded. When Viewstate is loaded, it is taken from the Request.Form object values, so you are seeing correct values there.

    • 0