Last week I was participating in a discussion thread about VB.NET and the Windows Forms. Matthew asked whether there was anything funky with the forms class that he should keep an eye out for. Those of us who were veteran users of VB 6 remember some of the odd behavior that cropped up from time to time when working with forms. Since Mathew was switching to VB.NET he wanted some tips pointing out potential gotcha's lurking in VB.NET - in particular he was looking for advice on .NET forms.
That got me to thinking. VB.NET is far less quirky then VB classic was in this regard. But there still are some specific gotcha's that only apply to VB.NET programmers. With that in mind I decided to start documenting a few of them here. If you have some ideas for more let me know. I will add them to the list.
For those of you who are tempted, please...no advice to switch to C# to solve the problem. These gotcha's are for the developer who chooses to, or is forced to code in VB.NET.