VB.NOT?
Some angst and attempted explanations related to VB .NET's incompatibility with VB6. IMO, this is just the latest in a long string of issues like this:
- The VB team comes up with a technology on their own, for their customers only.
- It becomes so popular other language users demand it.
- Microsoft implements the technology for everyone (all languages). Because it's for everyone, they have to do it in a different way than the VB team implemented it because when the VB team did the initial implementation they weren't thinking about how to design it so everyone could use it.
- The VB-specific version of the technology is deprecated.
- There is much wailing and gnashing of teeth.
Remember VBX controls? Remote Automation? The first versions of DAO? and ADO? The move to COM? Well, now it's the forms engine and the runtime.
12:34:02 AM 
|
|
