It normally would indeed preserve the selected value. Not because of ViewState but because of control state as the selected value of the drop down list is submitted to the server when you choose a new item (Drop down list can preserve their value even when ViewState is turned off).

However, in this case, after you've selected a new item, the user is redirected to the same page. A redirect means a new GET request, and thus there is no previous state / selection.

Does this help?

Imar

__________________
Imar Spaanjaars
http://Imar.Spaanjaars.Com
Follow me on Twitter

Author of Beginning ASP.NET 4.5 : in C# and VB, Beginning ASP.NET Web Pages with WebMatrix
and Beginning ASP.NET 4 : in C# and VB.
Did this post help you? Click the button below this post to show your appreciation!

OK this helped, but then why did we make the (!page.ispostback) we are posting back to the server, which means the code in the page_load is done only when the user opens the form, when he changes the drop down list, it won't go inside the IF condition, because it's a post back. right !?

Yes correct.

If you leave out the !IsPostBack check, the code in Page_Load would also fire after you selected item in the drop-down list, but before SelectedIndexChanged fires that redirects the user. Without the check, the drop down list would be reset to the previous value from the cookie and the new value would never be applied. Just take out the check to see for yourself how it works...

Cheers,

Imar

__________________
Imar Spaanjaars
http://Imar.Spaanjaars.Com
Follow me on Twitter

Author of Beginning ASP.NET 4.5 : in C# and VB, Beginning ASP.NET Web Pages with WebMatrix
and Beginning ASP.NET 4 : in C# and VB.
Did this post help you? Click the button below this post to show your appreciation!

you're the best :)