Quote Originally Posted by johnywalker View Post
No control arrrays.
Go on finish that sentence properly... "... at design time" ... seriously... thats' what this is all about when people civitch about the lack of control arrays... it's the lack of deisgn time support for them. Which is only half of it. Because you can easily create an aray of controls, just like any thing else. It just takes some effort. But as VB developers, we've gotten lazy and used to the IDE doing it for us. And so no that the IDE doesn't, we get all whiney. So if the lack of a built-in control array is your only reason for sticking with VB6 perhaps you should pull up your big boy programer undies and learn a couple new tricks.

As for releasing a new "updated" version of VB6. MS is never going to do that. I they were, they would have done it years ago, when the voices were loudest. They didn't then, they aren't going to do it now. No amount of petitions are ever going to change that. It's going to take a community effort to get it done... and even that is having trouble getting any kind of serious traction going. Just look at the threads in our own forums for that evidence. If there is ever a singular place where there is going to be a serous place where VB6 could be revived and moved ot the next place, it would be here... and yet... here we are.

Honestly, I don't think it's going to get much better than it is at the moment. You've got VB6 running on Win10. the RichClient library from Olaf, Krool's custom controls, and a couple of other pretty cool things out there. And a pretty hard core community at this point. To be perfectly one of two things will happen - VB6 as it is will become a cockroach language and keep on living, despite the harsh environments, it will keep going. Even after MS finds a way to mAke it so that the IDE "stops working" .... people will find a way to make shims or something to keep it going, or will develop a new IDE/compiler/run-time to keep it alive. I just don't see it happening right now.

-tg