My first Vs 2005 bug (and probably the last!!)

Since everyone's digging into Whidbey looking for bugs, I thought let me get one of my own :) Here is what I found. Ok..Ok.. I know its kinda little tacky..but oh what the heck.. I'm pretty sure I ain't finding any significant bug so might as well settle for a cosmetic one :)) The only thing that concerns me is that I hope MS doesn't slap the bug back on my face before anyone even visits the link from this blog :( I should consider sending this out to my friends and family. On Second thought - maybe not - probably even my eight year old nephew will laugh out loud if he finds out I submitted such a cheesy bug :-S

Subclassing in VB.NET

I must confess that I have no experience whatsover with subclassing and windows hooks in VB 6. However, reading this introduction, it looks like it would've been a while before I got a good hold of these techniques; Win32 API calls over the place - definitely not my cup of tea :) Ofcourse, that was in Visual Basic 6. DotNET seems to have made subclassing a lot easier - atleast subclassing and hooking onto windows messages in ones own application. You can read a brief introduction of how this can be accomplished here. DotNET eliminates the need of using Win32 APIs to a great extent atleast as far as subclassing is concerned. DotNET relies on, among other things, inheritance to achieve this. The Control class has a protected overridable WndProc which is in a sense the DotNET version of the Win32 API CallWindowProc. However, unlike CallWindowProc which took in 4 parameters, WndProc takes in just one - the message - which encapsulates all the parameters in a single structure. So, if one wants to modify the default behaviour of any control (including the form which eventually is inherited from the Control class), one can override the WndProc (in the left combobox in the code window, select the '(Overrides)' section and then you can select the WndProc from the right combobox) and then perform any action based on the message received.

What was MS thinking ??

This is what I came across when installing the MSDN for VS 2005 Beta 1.
What was Microsoft thinking?? How much of a rush were they in with the beta :)??

Some difference between VB and VB .NET

During the day, I work as a VB programmer. By the night, I'm messing around with VB .NET. I started this trend probably a month and a half back. Seemed to have picked up a little speed on the .NET side. Just for the heck, I penned down a few of the more obvious differences between VB and VB .NET. Not that its going to be awfully useful to anyone and ofcourse everyone's (or atleast the VB programmers moving to VB .NET) going to learn that somehow, but....
Anyway, this list is quite small since I stopped doing it after a while - kinda got boring and too much work :)
Click here to get the word document. Ofcourse, I could update the doc based on suggestions which are always welcome :)