Makes sense. No reason to rip it all out and go with something else.
>
Why do you prefer Typed DataSets?>
>Craig, I've been using Typed DataSets since .NET 1.0. Along the way, I've developed base class DataAccess code around this concept. I find no compelling reason to change to any other paradigm, given the fact that Typed DataSets, along with my server-side DataAccess classes, work just fine for all scenarios I've used (WinForms, WPF, and server-side), as long as I stay away from the dreaded TableAdapters (my DataAccess classes use DataAdapters).
>
>The only thing that will be different is for cross-platform apps (using Xamarin), which I've really only started playing with. Not all of the platforms will support DataSets for the UI (like, Windows Store apps) so I would use Lists of POCO classes on the front end. On the server-side, I still plan to get/save data to the database via DataSets ... probably.
>
>~~Bonnie
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer