Advertisement

Introduction

  • Gary Cornell
  • Jonathan Morrison

Abstract

We hope this book will be useful to experienced programmers of all languages, but this introduction is primarily aimed at Visual Basic programmers. Other programmers can jump to Chapter 2, to begin delving into an incredibly rich integrated development environment (IDE) backed by the first modern fully object-oriented language in the BASIC1 family. Programmers accustomed to Visual Basic for Windows may need some convincing that all the work they face in moving to VB.NET is worth it. Hence this chapter.

Keywords

Visual Basic Oriented Programming Executable Code Native Code Integrate Development Environment 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

Reference

  1. 1.
    Read BASIC as meaning “very readable-with no ugly braces....”Google Scholar
  2. 2.
    Its code name, “Thunder,” appeared on one of the rarest T-shirts around—it says “Thunder unlocks Windows” with a lightning bolt image. You may also see a cool screen saver that looks like the shirt.Google Scholar
  3. 3.
    Microsoft takes the word platform seriously. It even calls Windows a platform.Google Scholar
  4. 4.
    There is a conversion tool supplied with VB .NET, but we guarantee it will not ease the pain much. Any serious program will not convert well—you’re better off redoing them from scratch.Google Scholar
  5. 5.
    Dan Appleman, the wizard of the VB API, intends to write a book called something like The VB .NET Programmers Guide to Avoiding the Windows API. The .NET Framework is so full-featured that you almost never need the API.Google Scholar
  6. 6.
    Thus, the main difference between .NET and Java is that with .NET you can use any language, as long as you write it for the CLR; with Java, you can write for any platform (theoretically at least—in practice there are some problems) as long as you write in Java. We think .NET will be successful precisely because it leverages existing language skills.Google Scholar
  7. 7.
    Actually, this was not the bottleneck in a lot of cases. People can only click so fast and compiled code was irrelevant in most UI situations.Google Scholar
  8. 8.
    Inheritance is useful , but you should know that this is not the be-all, end-all of object-oriented programming, as some people would have you believe. It is a major improvement in VB .NET but not the major improvement.Google Scholar
  9. 9.
    Dan Appleman has a e-book that goes into this question at some length (available at www. desaware. com). Still, if you are browsing this chapter in a bookstore trying to decide, we hope the following are sufficient reasons for choosing VB .NET.Google Scholar
  10. 10.
    We are writing a book tentatively entitled C# for the Experienced (VB) Programmer for those who want to do this, but VB remains our first love, which is why we wrote this book first.Google Scholar

Copyright information

© Gary Cornell 2002

Authors and Affiliations

  • Gary Cornell
    • 1
  • Jonathan Morrison
  1. 1.BerkeleyUSA

Personalised recommendations