> Since now it's easy to make/use a collection for databinding, I guess > most of the reasons for using a dataset are eliminated. >
It sure would be nice to see if a DataSet is significantly worse than a collection. When you think about it, and given an axiom I really believe: "premature optimization is the root of all evil", I would like to think choosing a DataSet first is the right choice. If in some application you discover problems because the number of simultaneous occurances causes a memory bloat, or massive cpu ticks are needed to create and tear down your datasets (if it's proved that datasets are worse), the worst that can happen is that you refactor and use a custom collection. In the meantime, one less block of code to check into source control, one less library to maintain, one less skill to teach junior programmers, etc, etc, etc... You would want to do as similar comparison as possible, one simple table with one column, strongly typed, rows added at runtime, enforceconstraints off and the like. __________________________________________________ Do you Yahoo!? Faith Hill - Exclusive Performances, Videos & More http://faith.yahoo.com You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
