ADO.NET and ADO Examples and Best Practices for VB Programmers, Second Edition brings the popular first edition up to date with fresh insights and tips on COM-based ADO-and adds a voluminous section on the new ADO.NET technology.
Written specifically for COM-based ADO developers retooling for ADO.NET, this is a developer’s book, packed with practical advice on how to make code run faster, yet be easier to write and understand.
Veteran author William Vaughn guides you through the data access maze with working exapmles and numerous discussions of what works and what doesn’t. Derived from years of experience working with data access developers, Vaughn’s Best Practices are a set of techniques proven to drastically reduce overhead, problems, and confusion-for the developer, the system, and the entire team. While some are quite simple to implement, others require considerable knowledge and forethought to enable.
UP TO THIS POINT this book has been about COM-based ADO; from this point forward it’s all about the .NET Framework, ADO.NET, and to some extent about how Visual Studio .NET helps you build ADO.NET-based applications. The concepts and code discussed and illustrated here apply (in most cases) to .NET WinForms and ASP Web Services and other ADO.NET platforms.
To make the transition to .NET easier for you and to clarify how I view this new technology, I start by helping you get familiar with .NET, its new terminology, and the new ways it allows you to access your data. There are many tutorials on .NET, most of which clearly describe the technology, albeit each from a unique and distinct point of view. In this book, my intended target audience is the experienced COM-based ADO developer. In this second half of the book, I focus strictly on my personal area of .NET expertise: data access and especially, data access with SQLServer. You might sense a bias in favor of Microsoft SQL Server (guilty) and the Sql-Client namespace. Perhaps that’s because I’ve had more experience coding, designing, implementing, testing, and teaching SQL Server than any other DBMS system. Again, in most cases, the OleDb namespace implements the System.Data classes in much the same way. Sure, I point out areas where there seem to be differences between the provider implementations; but no, I won’t be getting into the Odbc .NET Data Provider. Because of Microsoft’s hesitancy to keep this provider up to date during the beta cycle, my technical editors and I were unable to include much more than a passing reference to this provider. Check my Web site for an update sometime after this book hits the streets for differences and issues.
Download ADO.NET and ADO Examples and Best Practices for VB Programmers
Written specifically for COM-based ADO developers retooling for ADO.NET, this is a developer’s book, packed with practical advice on how to make code run faster, yet be easier to write and understand.
Veteran author William Vaughn guides you through the data access maze with working exapmles and numerous discussions of what works and what doesn’t. Derived from years of experience working with data access developers, Vaughn’s Best Practices are a set of techniques proven to drastically reduce overhead, problems, and confusion-for the developer, the system, and the entire team. While some are quite simple to implement, others require considerable knowledge and forethought to enable.
UP TO THIS POINT this book has been about COM-based ADO; from this point forward it’s all about the .NET Framework, ADO.NET, and to some extent about how Visual Studio .NET helps you build ADO.NET-based applications. The concepts and code discussed and illustrated here apply (in most cases) to .NET WinForms and ASP Web Services and other ADO.NET platforms.
To make the transition to .NET easier for you and to clarify how I view this new technology, I start by helping you get familiar with .NET, its new terminology, and the new ways it allows you to access your data. There are many tutorials on .NET, most of which clearly describe the technology, albeit each from a unique and distinct point of view. In this book, my intended target audience is the experienced COM-based ADO developer. In this second half of the book, I focus strictly on my personal area of .NET expertise: data access and especially, data access with SQLServer. You might sense a bias in favor of Microsoft SQL Server (guilty) and the Sql-Client namespace. Perhaps that’s because I’ve had more experience coding, designing, implementing, testing, and teaching SQL Server than any other DBMS system. Again, in most cases, the OleDb namespace implements the System.Data classes in much the same way. Sure, I point out areas where there seem to be differences between the provider implementations; but no, I won’t be getting into the Odbc .NET Data Provider. Because of Microsoft’s hesitancy to keep this provider up to date during the beta cycle, my technical editors and I were unable to include much more than a passing reference to this provider. Check my Web site for an update sometime after this book hits the streets for differences and issues.
Download ADO.NET and ADO Examples and Best Practices for VB Programmers
