Prentice Hall PTR's new ADO.NET Programming in Visual Basic .NET -
Build powerful database apps and Web services fast, with VB.NET and ADO.NET!
With ADO.NET, you can build database-enabled applications and Web services with more speed, flexibility, and power than ever before. ADO.NET Programming in Visual Basic .NET teaches you all you'll need to know to make the most of ADO.NET - whether you're an experienced Visual Basic database programmer or not. The authors' realistic code examples and practical insights illuminate ADO.NET from its foundations to state-of-the-art data binding and application optimization.
Coverage includes -
The book concludes with a complete case study application - constructing a .NET version of the powerful ADO data control that VB 6 programmers loved, but isn't included in ADO.NET.
Introduction. Platform Issues. Version 6.x GUI Installation. Command-Line Installation. Version 7.x GUI Installation. Recap.
Introduction. Windows Application Start. Windows Service Start. Scripted Start. Command-Line Start. Remote Start. Stopping the Server. Recap.
Introduction. Creating a New Domain. Adding a Managed Server. Adding a Managed Server, Part 2-On the Managed Server Side. Recap.
Introduction. Basic Architecture. Multiple-Tier Architecture. Proxies. Recap.
Introduction. HttpProxyServlet. Apache. Netscape. IIS. Parameters. Recap.
Introduction. Communication. HttpClusterServlet. HTTP Servers. Configuration. Cluster Operations. Configuration in WebLogic Server 7.x. Recap.
Introduction. Connection Pools. MultiPools. Data Sources.
Introduction. Administering JMS. Clustering JMS. Messaging Bridges. Recap.
Introduction. Performance Tab. SNMP. Configuring SNMP.
Introduction. Tuning the JVM. Tuning WebLogic Server. Execute Queues. Recap.
Introduction. SSL. 6.x Security. 7.x Security.
by Bob Howell
Welcome to ADO .NET Programming in Visual Basic .NET. As a fellow VB programmer and developer, I wrote this book for two reasons:
My intent is not necessarily to win you over and get you to switch platforms. That is the job of Microsoft's marketing people. My intent is to show that .NET is a radical departure from previous versions of VB and that it is a first-class tool for serious development.
When I first started working with the beta versions of Visual Studio .NET, I could see from the very beginning that this was going to be a disruptive release, a term I adapted from sociology. In sociology, disruptive innovation refers to the invention of something so revolutionary that it changes the basic rules by which the society functions. The automobile, airplane, and personal computer are all examples of disruptive innovation.
Once the automobile was invented there was no reason to further develop horse-drawn buggies. So by calling VB .NET a disruptive release I mean that Visual Studio .NET is such a radical departure from what most VB Classic programmers are used to that it would require almost complete retraining to bring them to the point of being as productive as they were in their prior VB version. Having programmed in VB since Version 1.0, I remembered what the conversion from VB 3 to VB 4 entailed. That was the last time Microsoft radically changed the language to support 32-bit programming and operating systems such as Windows 95 and NT.
Microsoft also switched from the VB-specific VBX format component model to the new (at the time) OCX OLE-based component model. This caused a lot of consternation and discussion (read whining and complaining) among the programming community. If that seemed difficult, this time is not even remotely as easy. That was a breeze compared to this.
As I worked with Visual Studio .NET, however, I could see that this was much better than what we had in the past. VB Classic had grown from basically a scripting tool to a sophisticated development platform capable of creating line-of-business class systems. It also became bloatware, meaning the package became so large and cumbersome that with each new revision, we had to learn a whole new set of tools and wizards.
In the wider world of programming, VB Classic is an anomaly. It has its own proprietary IDE, its own runtime, a peculiar syntax, and its own proprietary forms package. None of these items works very well with other languages. VB Classic grew out of the early BASICs that came with old microcomputers. I remember Level II BASIC, the language that ran on my old (circa 1979) Radio Shack TRS-80 Model I, also known as the "Trash-80." While it still used line numbers, GoSubs, and Returns, it had the same basic syntax as VB Classic. That language evolved into GW-Basic that came with the original MS-DOS.
We then had Quick Basic, a cheap compiled version of GW-Basic. Then there was the Basic Professional Development System, a fully compiled and linked BASIC language for MS-DOS development. Finally came VB 1.0, which kept much of the syntax, statements, and functions of the older languages to try to win those programmers over to Windows development. If you don't believe that VB Classic evolved from those early languages, you should know that VB 6 still supports line numbers, GoSub, -Return, and GoTo. It also supports On-GoSub, an early form of a Select-Case statement. Microsoft doesn't advertise this, but it does work. Try it sometime. VB Classic has maintained that evolutionary path up until VB .NET.
With VB .NET, we now have a fully object-oriented programming language that rivals other languages, such as Java. The forms package is generic and no longer limited to use with just VB. You can actually pass entire forms across a network connection. While much of the syntax is the same (it is, after all, still BASIC), it has been standardized and brought into conformance with other languages. You no longer pass values into functions by reference as the default. The default is now by value, which is how virtually all other languages do it. Unfortunately, this will make transitioning difficult for many VB Classic programmers. This book is designed to ease that transition, and avoid the mistakes and wrong turns I made while hacking through it myself.
ADO .NET programming has a special connection with Visual Studio .NET, and we'll see both packages at their best and most powerful in this book.
These two packagesADO .NET and Visual Studio .NETare specifically designed to work together. Visual Studio bends over backward to make using ADO .NET easy, and I'll cover the Visual Studio .NET database tools like the Project Explorer, the various data adapter and dataset configuration tools, the query builder, and more in depth. In fact, the natural environment for ADO .NET programming is Visual Studio .NETand I think you'll agree as you read this book.
If this book is titled ADO .NET Programming in Visual Basic .NET, why do I keep referring to Visual Studio? Well, in the past, VB (and its variants, VBScript and VB For Applications) was the most natural environment for ADO database programming. The other Visual Studio tools (Visual C++, Visual Interdev, Visual FoxPro) could all use ADO, but since ADO was designed around the COM (Component Object Model) architecture, VB was the easiest way to use the package. With the advent of Visual Studio .NET, this has all changed.
Visual Studio .NET no longer uses COM as its underlying architecture. Instead it uses the Extensible Markup Language (XML) and Simple Object Access Protocol (SOAP). (You can still use your old COM objects in .NET, even ADO, but that is outside the scope of this book.) The common language runtime (CLR) interpreter allows all of the managed languages (VB, Managed C++, and C#) to utilize a common set of data types and interfaces so they can all use the same objects interchangeably. In fact, you can write components in C# and use them in VB and vice-versa. So while we will use VB .NET syntax in all of the examples and demonstrations in the book, the principles we are sharing will apply equally to C#.
This book covers ADO .NET programming using VB .NET, which means there's a great deal of material to work with: the basics of the ADO .NET object model, Web Services, typed and untyped DataSets, DataAdapters, ASP .NET, and DataBinding. ADO .NET is intended to be the future of data access as far as Microsoft is concerned, and we'll see it all here.
The short answer is that you will need Microsoft Visual Studio .NET Professional Version or higher. Any machine that will run that will be capable of executing the examples in the book. If you are not sure if your machine will run Visual Studio .NET, the requirements are:
If the entry price of Visual Studio .NET Professional makes you unhappy (the nonupgrade version is about $800), you can get a free 60-day evaluation copy from Microsoft. Or you can get your boss to buy it for you. Just convince him or her that the next big project cannot be done without it! Microsoft will love you and so will I. There is a "Standard" version of VB .NET on the market. It has a really great price, but, unfortunately, it lacks too many features to make it usable for this book.
You will also need some programming experience. It's good if you've programmed in previous versions of VB, but experience with any Basic language will do. If you've programmed in another object-oriented language, even better. Some experience with databases is also desirable. A decent understanding of basic SQL (Select, Update, Insert, and Delete) will help a great deal; we are not going to attempt to teach SQL. We will give you the basics, but there are other great books on SQL. The purpose of this book is to teach you how to use ADO .NET from within VB .NET and that is what we shall do. When you finish this book, you will be well-equipped to begin developing serious business applications in VB .NET.