Since you will probably compile and attempt to run the program if you're following along in code, this is a good time to mention another change that isn't documented in the new VB.NET, but it can trip you up if you're not expecting it.

If you're like me, you use the fact that you can experiment any way you like with an existing VB6 project without worrying too much about changing your original source code as long as you remember to answer "No" when VB6 asks if you want to save the project. VB6 doesn't touch your source until the files are actually saved at the end of your edit session.

The default for VB.NET, on the other hand, is to save your files automatically when you compile and run your program. So at the end of an edit session, you may close down the development environment after extensive changes expecting to be able to simply not save the project. Not so fast there, Pilgrim! The next time you open the project, you will discover that your experiments have wiped out your original source code.

Of course, like other things in VB.NET, all this has changed for a greater good. Versioning has been upgraded significantly in VB.NET with major changes such as side by side execution of different versions and automatic detection of the correct program version using VB.NET's new Manifest. It's all part of learning the characteristics of a completely new computer language.