<div>
Hi sbornstein2,<br />
<br />
Actualy this depends on your purposes. If you want to keep the functionality that DataSets give you &nbsp;(like offline operating with data and then put everything back to the database) then dataset is the better solution<br />
If you wan to write your logic for puting database or you want just to show the data withouth matter the data back to database then it is better dolution to use IList collections<br />
<br />
Regards<br />
Martin
</div>


Hi sbornstein2,

Actualy this depends on your purposes. If you want to keep the functionality that DataSets give you  (like offline operating with data and then put everything back to the database) then dataset is the better solution
If you wan to write your logic for puting database or you want just to show the data withouth matter the data back to database then it is better dolution to use IList collections

Regards
Martin

<div>
got ya. &nbsp;So it depends on when you want to use day DataReader in the SQLHelper to just get a static set VS inserting data into the DB etc?
</div>


got ya.  So it depends on when you want to use day DataReader in the SQLHelper to just get a static set VS inserting data into the DB etc?

<div>
<div class="content wysiwyg-content">
I am wondering when I should use an IList for gathering data arraylists etc. &nbsp;Thanks all
</div>
</div>


I am wondering when I should use an IList for gathering data arraylists etc.  Thanks all

Is it better to use an Interface such as IList instead of Datasets to fill Repeaters, controls etc?

The successor to Active Server Pages, ASP.NET websites utilize the .NET framework to produce dynamic, data and content-driven web applications and services. ASP.NET code can be written using any .NET supported language. As of 2009, ASP.NET can also apply the Model-View-Controller (MVC) pattern to web applications