Matt,

I can only comment on DataSets, because that's all I've been using. They are not as scary as you make them sound, plus a Typed DataSet gives you all the intellisense you need. SQL DataAdapters are not hard to use either. We've got a pretty robust base DataAccess class that abstracts all that stuff out so that the application developer really only needs to know the names of the Stored Procs they need to call in their own sub-classes. The base class handles most of the "under the covers" work automatically.

So, you've played with Linq to SQL, that's good. But, have you actually tried it for real, not just putting all that stuff on a Form (we all know that's not "best practice"). You've got to have the SQL connection string stored somewhere. You've also got to make it easily configurable (no hard-coded stuff!) ... it's been a few years since I tried Linq and I didn't think at the time it was the way we wanted to go. But, it was still new then and not fully developed ... maybe they addressed the issues I had with it at the time, but I'm sorry to say that I never went back and re-visited it (haven't had the time really).

~~Bonnie



>Newbie to .NET data apps here, coming from a Visual Foxpro background.
>
>I'm planning on an ASP.NET and/or Silverlight UI, and maybe some WPF client stuff too on our LAN too, so I want to craft a data access layer that can support all these front ends.
>
>My data will be in SQL server. I have already made a test run of pushing the data from Foxpro to SQL Server 2005. It went well. That gave me a SQL server data store to play with.
>
>Now, here are the data tools I played with so far, trying to get familiar with .NET data access:
>
>1. I've played with Linq-To-Sql, and made a test form using the typed objects and collections from L2S, and then populating some WPF listviews and other UI controls. That was cool. Linq is cool! WPF is cool. See screenshot of form here: http://twitpic.com/26w26/full
>
>and
>
>2. I've played with what I guess you'd call classic ADO.Net DataSets. Man, DataSets seem like a lot of work... A SQLConncetion A SQLCommand A DataSet A TableAdapter
>
>...and worst of all, I had to type SQL code within quotes, with absolutely no help from the IDE to to keep me from making typing errors, or writing just plain wrong SQL code, and I had to know the columns names from my data table every time. Lots of room for errors! And query parameters, yuck.
>
>So, let me ask.... does the .NET developer community really work with SQLCmds, DataSets, and DataTables to read and write data? Is that how it works?
>
>I know all about the O/RM battles out there, and EF too.
>
>It sure looks like you can hook up any of the UI controls from ASP.NET/Silverlight/WPF/and WinForms to either Object collections (via OR/M) or DataSets/DataTables, right? Is it always a choice between one of those two?
>
>So, it's decision time for me, but, I don't know that to choose. They all seem to work, but that darn DataSet thing just seems scary to me, but, somehow, it also seems to be commonly used.