Visual Basic Los Angeles CA

provided by:


For Dummies is a registered trademark of Wiley Publishing, Inc. in the United States and other countries. Used here by license.



To get started with Visual Basic 2008, I recommend that you jump right in and write software! And to help you with such an assertive approach, this article gives you just what you need to test the waters of the Visual Basic pool and get comfortable with its place in the larger Visual Studio environment. Then you can really get your feet wet as you build Hello World — your first VB 2008 Windows Forms application — right here in the first few pages! You find out how to launch Visual Studio 2008 (the development tool for your VB applications), how to start a new project, and how to build a form visually and make it work with code. Also in this section, I give you a glimpse into the deeper power of Visual Basic. Specifically, I introduce how VB 2008 integrates with the Microsoft .NET Framework and offer insight into what that means to you as a programmer.

Visual Basic’s Role in the Framework
Microsoft created the .NET Framework to make development for the various Windows operating systems easier. But because of the differences between Visual Basic 6.0 and Visual Basic 7.0 (the first .NET version), most VB developers found development much harder. For example, VB 7.0 made all variables into objects, which removed the programmer’s ability to define a variable type on the fly. But developing applications in .NET doesn’t have to be harder than it was in VB 6.0. The .NET Framework and Visual Basic 2008 can be powerful tools, and the trick is discovering how they work together through the Visual Studio Integrated Development Environment (IDE). Part of the difficulty that many programmers face when moving to the .NET Framework is the terminology, which can get confusing. I’d like to put the problem with terminology to bed right now, so check out this list of the potentially confusing terms used in .NET development:

Visual Basic 2008: The programming language described throughout this whole book. No longer can you run or load Visual Basic as a separate entity. It is simply one programming language that speaks to the Microsoft .NET Framework, which is the next term in the list.

.NET Framework: The layer that sits between the language (in this case, Visual Basic) and the operating system, which can be Windows 98, Windows Me, Windows 2000, Windows XP, Windows Server 2003, or any of the subversions of those (such as the Tablet PC edition). The .NET Framework layer serves to provide functionality based on the operation of the Windows system on which it resides, as well as to provide libraries for other functionality (such as math computations and database access).

Visual Studio 2008: The tool that you use to create any kind of application using any compatible programming language. Visual Studio replaces the Visual Basic 6.0 program that was formerly part of the Visual Studio suite (all individual suite components were labeled Version 6.0). When you go to write a new program in the .NET environment, you run Visual Studio 2008 and select the kind of program you want to write in the programming language you want to use. For example, you may choose to create a Windows Forms program using the Visual Basic language, just like the old days. Or you might want to write an application for a smart device using C#. You can also mix languages, for example, writing the forms in VB and the classes in C#.

Windows Forms: The new term for an old-fashioned Visual Basic application. This term refers to an application that is written using the .NET Framework and has a Windows user interface.

Web Forms: The term for an application with a Web page interface written using the .NET Framework. Creating a Web Forms application is very similar to writing a Windows Forms application.

Web services: The class libraries that are written using a standard defined by the same people who defined standards for the World Wide Web. Web services are used for interaction between divergent systems. The .NET Framework is what you may already know as the Win32 layer in the old Windows DNA system. Like the new .NET Framework, the Win32 layer gave you the ability to get to the functions of the operating system when developing for a Windows platform. Also, the .NET Framework includes a lot of adjunct functionality, such as math and data libraries, that makes programming a more cohesive experience. Basically, everything that Windows does is exposed by the .NET Framework. Specifically, the .NET Framework gives a programmatic name to nearly every object and event that Windows can control. A programmer can use that name to refer to anything existing in the operating system. Do you need to tell the printer to make two copies of your document? Try referring to My.Computer. Printers.DefaultPrinter.PrinterSettings.Copies = 2. Do you need to paint some item on the screen blue? Try referring to System. Drawing.Brushes.Blue. In this .NET world, the programming language becomes just a way to interact with the framework and, therefore, with the Windows operating system. All programs need a set of established rules to handle the flow (decisions, loops, and so on) within programs. Visual Basic provides one such set of rules, and the framework provides the objects and events to interact with.

provided by:


For Dummies is a registered trademark of Wiley Publishing, Inc. in the United States and other countries. Used here by license.

Los Angeles Dodgers

(323) 224-1500
1000 Elysian Park Avenue
Glendale, CA