ADO .NET Programming provides a sophisticated reference to ADO .NET solution development. Aimed at database programmers with a working knowledge of the .NET Framework, this book dissects the ADO .NET component model and provides real-world examples demonstrating how ADO .NET can be used to manipulate data from different sources.
* Discover the differences between ADO and ADO .NET.
* Learn how to interact with databases using the Connection, Command, DataReader, and DataAdapter components and how to manipulate data with the DataSet component.
* Understand how XML is integrated with ADO .NET and learn the best ways to use that technology in your programs.
* Learn the subtle aspects of migrating ADO applications to ADO .NET.
* Develop and manipulate a data warehouse with ADO .NET and develop your own .NET data provider.
The appendixes include references to the new object-oriented paradigm of VB .NET, database normalization, views, stored procedure and trigger programming, and techniques for adding SQL functionality.
User review
Ten things that are wrong, wrong, wrong with this book
1. I did not read chapter 1.
2. Chapter 2 start off with a short paragraph warning the reader that the discussion on data provider is very `conceptual`. And then it proceeded to list down the various properties and methods in ALPHABATICAL order -of Connection, Command, DataReader, DataAdapter - right to the end of the chapter. I do not think reading a dictionary like listing of properties and method of each object is any thing `conceptual`-neither is it the preferred learning method encourage throughout the English speaking world -which I presumed this book is targeted for since it is written in English. I could be wrong, though.
3. Chapter 3 - see chapter 2 -this time we have ALPHABATICAL soup for DataSet.
4. Chapter 4 -in some 20 odd pages it covered Data binding, window form, console application, window services, ASP.NET, XML web services, Stored Procedure, SQL statement, Data Warehousing, Protecting the Application, and more (or is it less?). There are some codes (some `class` code I think) litter around here and there, BUT, there is not a single example showing you how to create any of the thing that he discussed. PErhaps may be this is also a `conceptual` chapter. Could have fool me.
5. This is a chapter in XML. It defied all my past, present, and future attempts to understanding it. Also at this point -I noticed that with half the book gone -we have not yet create a single dataconnection or dataset -chapter 2 and 3 are sheer `conceptual`, remember?
6. Chapter 6 is practical case study -codes are everywhere but there is still no sign on how to drag a dataAdapter from the toolbox to the window form and setup a connection. Perhaps should rename Theoritical case stufy.
7. Chapter 7 -see chapter 6.
8. See chapter 8.
9. Chapter 9 manipulating multidimensional data -something to do with OLAP solution, SQL server 2000 Analysis service. Oh, I just noticed that codes on this chapter includes a full view of the highly sought after `Windows Form Designer generated code`- but of course I am left wondering how the form looks like -it was never shown.
10. Sorry to say this, but arguably the only wrong thing that they manage to do right is not to have chapter 10. I congratulate myself for finally able to end the tremendous suffering of going through this book.
User review
IF THIS IS the best ADO.NET book then GOD HELP US
I gave this book 2 stars because of the VERY misleading title.
(I also took the book back to the store)
The book does not even come close to being an ADO.NET book. It states Learn How To interact with databases using the Connection, Command, DataReader, and DataAdapter Components and how to manipulate data with the dataset component.
This is a JOKE. Chapter 2 Interacting With Databases is nothing more than a list of the objects mentioned above and their properties and methods. NOT EVEN AN EXAMPLE on how to properly use them.
The book should have been named more for the interaction of ADO.NET and XML, because that is what most of the focus appears to be on.
But what the book does cover is very well written !
User review
The best ADO.NET book (if you are a VB.NET Programmer)
I got this book a couple of days ago from Amazon. When I opened the book that I so eagerly waited for, It put me off to find that 100% of the samples in this book are in VB.NET (Oh! Did I forget to tell you that I am a C# programmer). Though ADO.NET framework is the same for any .NET language, It is a little hard to follow the flow of the sample program codes when you don't understand the language. So, the authors should have named this book `ADO.NET Programming for VB.NET programmers`.
Having said that, the topics this book covers seem to be very good. This book does teach you how to use ADO.NET (efficiently - and that's important). The bottom line is, it is an excellent book. I took a star away from my rating for not letting me know this was a VB.NET book.
User review
The best ADO.NET book (if you are a VB.NET Programmer)
I got this book a couple of days ago from Amazon. When I opened the book that I so eagerly waited for, It put me off to find that 100% of the samples in this book are in VB.NET (Oh! Did I forget to tell you that I am a C# programmer). Though ADO.NET framework is the same for any .NET language, It is a little hard to follow the flow of the sample program codes when you don't understand the language. So, the authors should have named this book `ADO.NET Programming for VB.NET programmers`.
Having said that, the topics this book covers seem to be very good. This book does teach you how to use ADO.NET (efficiently - and that's important). The bottom line is, it is an excellent book. I took a star away from my rating for not letting me know this was a VB.NET book.
User review
The best ADO.NET book around.
If you seriously want to learn all about ADO.NET then look no further, this is the book for you. The book is my favourite ADO.NET book, and acts as a very good reference. The book also has really good examples and the appendix is also valuable resource for a refresher on database issues such normalization, views, stored procedure and trigger programming.
