A development guide to ADO. NET provides a helpful tutorial, accompanied by real-world examples, to Microsoft's Universal Data Access Strategy, and shows how to use ADO. NET across a variety of data platforms. Original. (Intermediate)
"synopsis" may belong to another edition of this title.
Shawn Wildermuth is the founder of ADOGuy.com and has been building data-driven software for more than sixteen years. Shawn has developed database applications for a variety of fields, including accounting, real estate, Internet, and medicine. His articles can be found in a number of journals, including MSDN Magazine and Windows 2000 Magazine.
"This is my favorite book on ADO.NET. The author clearly has an extensive understanding of the subject matter. It is useful not only for expert data access programmers but also for weekend code warriors."
&;Glenn Thimmes, Senior Software Engineer, New Dawn Technologies.Formerly Develop Support Engineer (WebData), Microsoft Corporation
Pragmatic ADO.NET is a practical guide to using the first data access services designed specifically for Web-based applications. This tutorial provides developers with a clear introduction to ADO.NET, and gives practical solutions for using it effectively.
The book begins with a concise history of Microsoft's Universal Data Access strategy and the evolution of technology that has led us to ADO.NET. The core of the book demonstrates how to use ADO.NET to interact with databases and the rest of the .NET framework. In addition, readers learn by example the best practices for using ADO.NET to build scalable, high-performance systems. Pragmatic ADO.NET includes numerous code examples in C#, and a companion Web site located at www.adoguy.com/book features implementations in Visual Basic .NET and C#, along with updates on the technology. The book concludes with an appendix detailing strategies for migrating from ADO to ADO.NET.
Readers will learn how to:
The combination of concise coverage, helpful explanations, and detailed examples makes Pragmatic ADO.NET an important guide for all developers looking to gain a working knowledge of ADO.NET.
Books in the Microsoft .NET Development Series are written and reviewed by the principal authorities and pioneering developers of the Microsoft .NET technologies, including the Microsoft .NET development team and DevelopMentor. Books in the Microsoft .NET Development Series focus on the design, architecture, and implementation of the Microsoft .NET initiative to empower developers and students everywhere with the knowledge they need to thrive in the Microsoft .NET revolution.
ADO.NET is not ADO. This is the most important fact that this book tries to convey. Understanding ADO.NET is not just about how to get database data or how to update the database—it requires an understanding of why it was built. ADO.NET takes a completely different approach in accessing databases than older Microsoft data access strategies.
This is not your father's ADO.This book intends to be neither a reference nor an "internals" book of how ADO.NET works. It is geared toward helping day-to-day developers get their jobs done. This book intends to give clear advice on how to use ADO.NET.
This book is squarely aimed at developers who have a basic understanding of .NET and of databases. It is intended to help day-to-day developers get their job done. It does not assume prior experience with ADO, though it does build somewhat on that knowledge if it exists.
Part I is intended to get you started with the basics.
Before the book explains how to work with ADO.NET, it explains why ADO.NET was written. Chapter 1 discusses the history of Microsoft data access to explain how we got to ADO.NET.
Before we can do anything with a database, we must know how to connect to it. Chapter 2 is all about getting connected to databases through ADO.NET. This includes a discussion of how connection strings work, connection pooling in a variety of managed providers, patterns for connection creation, and how to minimize connections to the database.
Our only interface with the database is to issue commands and deal with the results of those commands. This chapter focuses on how to get the database to do work for us by using Command objects. This includes explanation of how to use the Command objects with simple SQL statements, parameterized queries, stored procedures, and batch queries.
DataReaders are ADO.NET's method for getting tables from the database. In Chapter 4, the book explains how to use DataReaders to access database information and shows an example of writing a class that uses the DataReader as its data source.
The DataSet is the heart of ADO.NET. To use the DataSet effectively, we must examine how it can be used to solve our day-to-day problems.
This chapter explains exactly what DataSets are and why you should use them. It covers the many ways to make DataSets, including using DataAdapters, XML, and code to create them. A complete discussion of how to use DataSet schema is also included in this chapter.
Typed DataSets are a useful tool that allows you to have code that adapts to changing schema. Chapter 6 explores this new programming model where we create typed DataSets and use them as the basis for business logic layers that are typically all handwritten. This chapter also shows how to create typed DataSets from within Visual Studio .NET as well as from the command line.
Now that we know how to create DataSets, we need to understand how to use them to manipulate data and how the data are structured inside them. Chapter 7 explains how the DataSet model works and how you can use it to get your job done.
Once we have manipulated data within a DataSet, we have to have a way to update the database with those changes. Chapter 8 walks you through how to plan for disconnected concurrency. It includes examples of using the built-in optimistic concurrency and how to implement pessimistic and destructive concurrency. In addition, the chapter discusses how to handle concurrency violations and gives concrete examples of one solution for dealing with concurrency violations.
Now that we know how to access data, manipulate it, and update the database with the changes, we need to know how we can get ADO.NET to interact with the rest of the .NET framework.
XML is just data. ADO.NET is the data framework for .NET. These two facts come together to show why ADO.NET is so tightly integrated with the XML framework to allow for database data to be commingled with database data. Chapter 9 explores the way to treat each type of data like their brethren.
In .NET, there are two forms-based technologies: Windows Forms and Web Forms. Luckily, ADO.NET containers (DataReaders, DataSets, and Data-Tables) all support direct data binding. Chapter 10 shows you how.
This chapter brings it all together with concrete design suggestions for how to build scalable, high-performance systems. In addition, the chapter lists a set of best practices for using ADO.NET and database development in general.
We cannot pretend that all .NET code will be all new development. Thereare many developers out there who have code to migrate to .NET. Thisappendix lists a number of strategies for living in a mixed system whereyou need to have ADO.NET data structures reading ADO structures, andvice versa.
"About this title" may belong to another edition of this title.
Seller: old aberdeen bookshop, Aberdeen, United Kingdom
Soft cover. Condition: Very Good. A very clean copy, few signs of wear, appears unmarked. may incur some extra postage (at cost) outside the UK. Seller Inventory # 015158
Quantity: 1 available
Seller: Bay State Book Company, North Smithfield, RI, U.S.A.
Condition: very_good. Seller Inventory # BSM.16YHR
Seller: WeBuyBooks, Rossendale, LANCS, United Kingdom
Condition: Good. Most items will be dispatched the same or the next working day. A copy that has been read but remains in clean condition. All of the pages are intact and the cover is intact and the spine may show signs of wear. The book may have minor markings which are not specifically mentioned. Seller Inventory # rev2207683831
Quantity: 1 available