Preface
From 1992 to 1997, 95% of my development was done in Visual Basic, and about 5% of my development involved writing components for Visual Basic using the Microsoft Foundation Classes (MFC) in C++. Then, in 1998, I received an offer from a company to develop a set of COM components using a class library called the ActiveX Template Library (ATL) exclusively in C++. At the time I took the position, I thought I knew COM fairly well, and although I knew the C++ side of development would be a little difficult, I was convinced that within a few months I would be able to master it. Boy, was I in for a big surprise! After a few days, I realized that I knew very little about COM. In fact, I learned that, in many ways, Visual Basic shields us from knowing about COM. Part of me thought, “That’s what VB is for—to hide you from the details of the technology so that you can be more productive.”
After a few months at the job, I realized that, although the goal of Visual Basic is to hide the architecture so that we can be more productive, it turns out that there are many times in Visual Basic development when the technology sneaks out from under the covers. Once in a while, you will see options like DLL Base Address or Threading Model and wonder, “Should I turn that on?” “Should I change that number?” “What exactly does that mean?” The most frustrating thing is being faced with the technology and not knowing how to solve a simple problem only because VB has done such a good job at hiding things ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access