Moving to VB .Net

By: Hermawih Hasan

More than a year ago, I bought a book: Moving to VB .NET: Strategies, Concepts, and Code by Dan Appleman, Apress. I always like a book which tells about the concepts of something. I even bought a book for beginner from the same author and the same publisher: How Computer Programming Works.

From that book of VB .NET, without even trying any code from the book, I know that I will have so many works to do if I convert my VBA Codes to VB .NET. There is a paragraph that really caught my attention from page 110.

"You may have gotten the idea that I’m not terribly excited by structures. This may seem odd because under VB6, user-defined types had some major advantages over object types. Because they could hold fixed-length arrays and fixed string data, they offered an efficient way to transfer data in large blocks. They also had less overhead than objects. These advantages are not nearly as compelling under VB .NET."

For me that is the most important part of the book. Why? Because I have so many user-defined-types in my VBA Coding that must be changed. If I could get one of the most important thing in only one paragraph, why then I bother reading a book from beginning to the end words by words.

I think the book is an excellent source for any one who is thinking to learn VB.NET someday. If anything that is not correct about the book, probably the suggestions from the back cover of the book:

"Dear Reader,

If you are looking at this book, you are a VB6 programmer who is trying to figure out what to do about Microsoft .NET (if you aren’t, this is not the book for you). You might be trying ... "

I am not VB6 programmer but I found the book suit to my purposes.