I started using Visual Basic back when version 2.0 of the product was still in vogue. As a result, I picked up some pre-.NET coding habits that have been hard to break, even with my full-time focus on .NET code. I've reached a level of comfort in my Visual Basic coding, and that comfort shows in my .NET programming style.
As I mentioned in earlier chapters, many of the features that previously existed in Visual Basic before .NET were moved out of the language and into Framework classes. The most noticeable of these were the mathematics features now found in the
System.Math class. But there were other non-math Visual Basic language keywords that also became class methods. Many of these appear in the
Microsoft.VisualBasic namespace, including methods such as
When I wrote the Library Project code, I freely used some features found in the
Microsoft.VisualBasic namespace. Although I don't have a problem with this practice, you may encounter other Visual Basic developers who don't agree with how I've written the code. They point out that most, and possibly all, of the features in
Microsoft.VisualBasic have Framework Class Library (FCL) equivalents, and these should be used for reasons of compatibility with other .NET languages and systems.
A key example is the
MsgBox function. I've used it throughout the Library source code. The keyword
MsgBox has always been a part of the Visual Basic language, but beyond its continued existence in