A Programmer's Introduction to Visual Basic.NET_Craig Utley
Why Does This Book Exist?
This book is meant to give you a head start on the changes from Visual Basic to Visual Basic.NET (VB.NET). Most of the book assumes that you are comfortable with Visual Basic 6.0 (VB6), so the book endeavors to be a quick introduction to the major differences between VB6 and the new VB.NET. I’ve been using Visual Basic since version 1.0. The most dramatic shift had been in the move from VB3 to VB4, when class modules were introduced, and VB started on its long, slow path to becoming object oriented. For the first time, you could build COM components in VB, leading to an explosion in n-tier application development. VB4 brought COM development to the average programmer, so it was no longer a technology known only to a few C++ developers. When I first started looking at the differences between VB6 and VB.NET, I realized that the change would be even more significant than it had been from VB3 to VB4. I thought it would be good to put together a book that helped VB6 developers transition to VB.NET. To that end, I pitched the idea for a book named something like Migrating from VB to VB.NET to a couple of different companies. Sams Publishing liked the idea, and one day they called me and asked me about doing a miniature version of the book…in three weeks.
I don’t know who was crazier: Sams, for asking for the book in three weeks, or me, for agreeing to do it. Then, Sams said they were giving the book away, and I thought they had really lost it. Still, the mission was clear: create a book that targets Visual Studio.NET, Beta 1. Then, the day after I finished the book on Beta 1, Sams made the decision to release a book based on Beta 2 instead. Although I can’t say I was thrilled, I think it was the right decision. There were significant changes between Beta 1 and Beta 2. Microsoft says there will be far fewer changes between Beta 2 and the final product, so this book should have a much longer shelf life than a book based on Beta 1. There is no doubt: VB.NET will be an exciting change for us all. There is so much new material to learn that it can be somewhat daunting at first. However, the benefits of the .NET Framework are significant, and in the end can greatly reduce the effort required today to build enterprise-ready distributed applications.
This book will be followed by a much more comprehensive book based on the final version of Visual Studio.NET (VS.NET). The good news is that, as previously mentioned, the changes between Beta 2 and the final product should be far less dramatic than those changes between Beta 1 and Beta 2. Having said that, however, realize that there will be changes before Visual Studio is released.
Why VB.NET Instead of C#?
A lot of press has been given to the new language Microsoft has created: C# (pronounced “C-Sharp”). This is a new language, based on C/C++. C#, like VB.NET, is built specifically for the .NET Framework, and much has been written about it. Given all the hype, some people might wonder why they should choose VB.NET over C#. Although both VB.NET and C# projects are created in the Visual Studio.NET environment, VB.NET was created specifically for VB developers and has a number of unique features that make it a great choice for building .NET applications. VB.NET is still the only language in VS.NET that includes background compilation, which means that it can flag errors immediately, while you type. VB.NET is the only .NET language that supports late binding. In the VS.NET IDE, VB.NET provides a dropdown list at the top of the code window with all the objects and events; the IDE does not provide this functionality for any other language. VB.NET is also unique for providing default values for optional parameters, and for having a collection of the controls available to the developer. Don’t forget that C#, like its C and C++ brethren, is case sensitive, something that drives most experienced VB developers crazy. In addition, C# uses different symbols for equality (=) and comparison (==). Finally, let’s face it: If you know VB, you are further down the road with VB.NET than you are with C#. Even though much has changed, the basic syntax of VB.NET is similar to VB, so you already know how to declare variables, set up loops, and so on.
As you can see, VB.NET has some advantages over the other .NET languages. If you’re curious about the advantages of VB.NET over traditional VB, you’ll have to read this book.
Who Should Read This Book?
This book is targeted at current VB developers. If you don’t know VB, parts of the book might not make sense to you. The goal here is to cover what has changed. So, if something hasn’t changed, I have to assume that you already know it. If you know VB, and want to learn VB.NET or at least see what it can do for you, this book is for you. If you are currently using Visual InterDev to create Web applications, this book is also for you, because Visual InterDev has been integrated throughout Visual Studio.NET. This means you can create Visual InterDev–like Web Applications using VB.NET (and C#). You get several advantages with this new approach, including the ability to write in full VB.NET instead of VBScript, and the advantages of .NET’s Web application architecture (ASP.NET) over the current ASP model are significant. No matter what you will be doing with VB.NET, the place to start is with the .NET Framework. Without understanding the .NET Framework, you won’t be able to write good VB.NET applications, regardless of whether they are Windows or Web applications. Therefore, prepare to get started by examining the .NET Framework.
Download: A Programmer's Introduction to Visual Basic.NET_Craig Utley
This book is meant to give you a head start on the changes from Visual Basic to Visual Basic.NET (VB.NET). Most of the book assumes that you are comfortable with Visual Basic 6.0 (VB6), so the book endeavors to be a quick introduction to the major differences between VB6 and the new VB.NET. I’ve been using Visual Basic since version 1.0. The most dramatic shift had been in the move from VB3 to VB4, when class modules were introduced, and VB started on its long, slow path to becoming object oriented. For the first time, you could build COM components in VB, leading to an explosion in n-tier application development. VB4 brought COM development to the average programmer, so it was no longer a technology known only to a few C++ developers. When I first started looking at the differences between VB6 and VB.NET, I realized that the change would be even more significant than it had been from VB3 to VB4. I thought it would be good to put together a book that helped VB6 developers transition to VB.NET. To that end, I pitched the idea for a book named something like Migrating from VB to VB.NET to a couple of different companies. Sams Publishing liked the idea, and one day they called me and asked me about doing a miniature version of the book…in three weeks.
I don’t know who was crazier: Sams, for asking for the book in three weeks, or me, for agreeing to do it. Then, Sams said they were giving the book away, and I thought they had really lost it. Still, the mission was clear: create a book that targets Visual Studio.NET, Beta 1. Then, the day after I finished the book on Beta 1, Sams made the decision to release a book based on Beta 2 instead. Although I can’t say I was thrilled, I think it was the right decision. There were significant changes between Beta 1 and Beta 2. Microsoft says there will be far fewer changes between Beta 2 and the final product, so this book should have a much longer shelf life than a book based on Beta 1. There is no doubt: VB.NET will be an exciting change for us all. There is so much new material to learn that it can be somewhat daunting at first. However, the benefits of the .NET Framework are significant, and in the end can greatly reduce the effort required today to build enterprise-ready distributed applications.
This book will be followed by a much more comprehensive book based on the final version of Visual Studio.NET (VS.NET). The good news is that, as previously mentioned, the changes between Beta 2 and the final product should be far less dramatic than those changes between Beta 1 and Beta 2. Having said that, however, realize that there will be changes before Visual Studio is released.
Why VB.NET Instead of C#?
A lot of press has been given to the new language Microsoft has created: C# (pronounced “C-Sharp”). This is a new language, based on C/C++. C#, like VB.NET, is built specifically for the .NET Framework, and much has been written about it. Given all the hype, some people might wonder why they should choose VB.NET over C#. Although both VB.NET and C# projects are created in the Visual Studio.NET environment, VB.NET was created specifically for VB developers and has a number of unique features that make it a great choice for building .NET applications. VB.NET is still the only language in VS.NET that includes background compilation, which means that it can flag errors immediately, while you type. VB.NET is the only .NET language that supports late binding. In the VS.NET IDE, VB.NET provides a dropdown list at the top of the code window with all the objects and events; the IDE does not provide this functionality for any other language. VB.NET is also unique for providing default values for optional parameters, and for having a collection of the controls available to the developer. Don’t forget that C#, like its C and C++ brethren, is case sensitive, something that drives most experienced VB developers crazy. In addition, C# uses different symbols for equality (=) and comparison (==). Finally, let’s face it: If you know VB, you are further down the road with VB.NET than you are with C#. Even though much has changed, the basic syntax of VB.NET is similar to VB, so you already know how to declare variables, set up loops, and so on.
As you can see, VB.NET has some advantages over the other .NET languages. If you’re curious about the advantages of VB.NET over traditional VB, you’ll have to read this book.
Who Should Read This Book?
This book is targeted at current VB developers. If you don’t know VB, parts of the book might not make sense to you. The goal here is to cover what has changed. So, if something hasn’t changed, I have to assume that you already know it. If you know VB, and want to learn VB.NET or at least see what it can do for you, this book is for you. If you are currently using Visual InterDev to create Web applications, this book is also for you, because Visual InterDev has been integrated throughout Visual Studio.NET. This means you can create Visual InterDev–like Web Applications using VB.NET (and C#). You get several advantages with this new approach, including the ability to write in full VB.NET instead of VBScript, and the advantages of .NET’s Web application architecture (ASP.NET) over the current ASP model are significant. No matter what you will be doing with VB.NET, the place to start is with the .NET Framework. Without understanding the .NET Framework, you won’t be able to write good VB.NET applications, regardless of whether they are Windows or Web applications. Therefore, prepare to get started by examining the .NET Framework.
Download: A Programmer's Introduction to Visual Basic.NET_Craig Utley

0 comments:
Post a Comment