Hi Imar,

I took some initiative and tried to make a slideshow page for a picture album. Conceptually, I created an array, loaded all the images (file locations) for an album into the array, and then saved the array in ViewState. Then on a 4 sec timer, I get the next image in the ViewState array (using another viewstate to keep index count).

QUESTION: Is this an "Ok" approach? I understand that if I had a ton of images (lots of data), then I risk ViewState getting bloated. But then, I thought I could always limit the array load to keep ViewState manageable, and then just create another array to load another set of pictures when the user gets to that point, etc. On a conceptual level, is there a better approach? If so could you mention, in general terms, the better approach? Or is this method "ok"? TIA.

Hi there,

For small sets of images this would work fine. But, as you indicated, you'll run into issues when the number of images increases. Personally, I would store just the image index and recreate the array at each postback. This way, your code automatically scales in case the number of increases.

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!