No clue. Frankly, I'm absolutely not interested in .NET, so naturally I don't follow the headlines. Traditionally VB used OCXes and stuff like that that can be roughly compared to VCL components, but whether that's the case with .NET I don't know...Prof.Wizard said:PS. I think I read somewhere that MS's .NET in VB is using something similar to Delphi's VCL components. Is it true?
NO!!!PPS. Can you write me one darn positive thing about VB?!?
Ok, ok, there are obviously some things about VB that could be called positive, but that would very much depend on what's your angle on things...
For starters, one thing VB has going for it is that you can teach a bloody monkey to code some basic stuff in VB. Sometimes that is important. The drawback (I'll bet you knew this was coming! ) of course is that as a result all of VB code looks like it was written by a horde of monkeys!
Also, if you were to spend your entire development career revolving around small things in M$ Office in Windoze, VB would blend in very nicely - you'd be able to code entire (albeit somewhat slow, ugly and backwards) applications in VB, customize Office with macros and stuff in VBA (Visual Basic for Applications), really stress out Access (and possibly Excel - I did quite a bit of former but haven't tried any Excel mangling) - all that without ever leaving the comfort of your VB bubble. But of course, there are always alternatives, often much better alternatives to such mindset...
I think I also had another "positive" thing to add, but it slipped my mind... I'll add it if I recall it later on.