On Aug 6, 7:58 pm, welzie <[email protected]> wrote: > @Cerebus: That is EXACTLY why I posted it. However I have received > zero response so far. I am left to assume my thought on data > providers and ado.net are correct.
Your blog post while opinionated at times does hit the mark mostly. It is unconventional because I have rarely read such an interpretation of ADO.NET. At the same time, it is not thought provoking enough or detailed enough to merit a deluge of comments by readers. > Do most .netters only concern themselves with the classes that are > called ado.net(DataTable, DataSet) and forget or ignore the data > provider classes Command, Connection, DataReader? Firstly, it is my opinion that everything within the System.Data namespace (and child namespaces) is part of ADO.NET. Not just two or three classes. ADO.NET is much more than a set of classes, it's a way of accessing data. So, I wouldn't say that. What makes you come to such a conclusion?
