Visual Basic

It is imperative that your focus remain open minded when approaching the subject of programming. There are numerous different languages, each with their own strengths, weaknesses, and functionality in relation to the classification as an object oriented form of application design. Unfortunately, many programmers have developed a bias towards Visual Basic (VB) throughout the years primarily because earlier editions claimed to be object oriented, however, lacked implementation inheritance capabilities or method overloading features (Lhotka, n.d.). This is where VB.NET steps into action and resolves these minor fallacies.

“Visual Basic .NET is a fully object-oriented programming language, which means it supports the four basic tenets of object-oriented programming: abstraction, encapsulation, inheritance, and polymorphism” (Hamilton, n.d.). It bridged these so-called gaps between Visual Basic and object-oriented design; possessing an enormous amount of potential. In a sense, VB.NET enforces a basic programming principle by reiterating that objects are composed of a physical state and then trigger an event or behavior that complete them. At the developer level, we need an environment that allows us to work with each of these intrinsic components as if they were one. Visual Basic.NET does exactly that.

Every programming language has their unique advantages and disadvantages, with Visual Basic always being monitored under a microscope per say. One of the strongest benefits worth mentioning is VB.NET’s new standard for implementation inheritance. This allows the user to expound upon a class, by inheriting from it, while using it as the foundation for building newer classes (Utley, 2001). Another bonus is the built in debugging tool that allows multiple languages running the .NET Framework to be debugged with a single tool. Lastly, some developers prefer VB.NET for the simple fact that “components can be run locally, without requiring the calling application to go to the registry to find components” (Utley, 2001) and because Windows services are processed natively.

In closing, where the older versions of Visual Basic lacked, Visual Basic.NET has picked up the slack. Many programmers fail to look past these shortcomings, and could very well be limiting the potential