Printable View
CyberHawke is correct. http://vr6.pharfruminsain.com/VWVortex/thumbsup2.gif
Besides,... converting a 40,000 line VB6 project into VB.NET is the reason we have jobs! :D
Take advantage of the opportunity to improve the application by converting it yourself. I'm sure you'll easily find many new ways that the program will work better and smarter with all the improvements .NET provides.
Pantomimes and Americans...
"few years ago, when I first started using the Internet, I was corresponding with a young lady from America. In the course of conversation I mentioned that I had to leave to go and rehearse for this year's panto. The lady in question didn't have any idea of what I was talking about. I am again in the middle of rehearsals for panto, and thought this might be an opportune moment to explain, where necessary, the great British tradition of pantomime.
"
http://gouk.about.com/cs/theatre1/a/pantos.htm
I am no fan of Gee What Bush btw...
Not quite sure what you are asking.Quote:
Originally posted by birthjay
Thanks folks.
Are there any articles at Microsoft (or elsewhere) that support what has been said here?
Thanks!
Look at Control Arrays in MSDN Help (2003 version)
Quote:
" Visual Basic .NET and C# allow you to duplicate some of the functionality commonly associated with control arrays. For example, you can use delegates to bind events from multiple controls to a single event handler. However, it might be more convenient to incorporate that functionality into a single dynamic, easy-to-manage component. In this article you will create a component that uses the following:
A collection to index and sort your controls. A collection of buttons will be used for demonstration purposes.
An event handler to handle the click event from your derived button.
Code to allow referencing the control and its members by index.
Code to dynamically add and remove controls from your form. "
You're driving this thread crazy ! Control arrays suckx . This is my 2cent . :)
If it bothers you that much - simply don't get involved.Quote:
Originally posted by Pirate
You're driving this thread crazy ! Control arrays suckx . This is my 2cent . :)
So far all responds were leading toward WORK ARROUNDs especially by CyberHawke. The whole point of having ControlArray is be able to reference group of controls by INDEX and someone's already pointed it out. Instead of such extremly simple way we have to do all that nonsence discussed in this thread and beyond.
Regardless of any inputs, opinions and whatever - Control Array is one very powerfull feature .NOT could have !!!
As I said before, those who can adapt will, and those who cannot ....Quote:
Originally posted by RhinoBull
Regardless of any inputs, opinions and whatever - Control Array is one very powerfull feature .NOT could have !!!
Control Arrays offer no specific benefit which is why the engineers at Microsoft decided to drop support for them, it was not an oversight, it was intentional.
btw, most of the posts I have made to this increasingly indigestible thread had to do with re-writing your VB6 code into VB.NET code in lieu of using the upgrade wizard . . and I'm not gonna rehash that again.
Finally if you consider it .NOT, then why are you using it?
I have been using VB since before it was even called VB, I think I still even have a set of the two original disks (floppies) that version 1.0 came out on laying around here somewhere :p
I've watched VB mature over the years, gaining functionality and adding support for developer requests eg. database support v3, and OO support, v5, to finally fully supporting OO in the .NET release 1.0. If anyone thinks that pre-.NET versions of VB are better than the .NET offering, by all means, be my guest, please do continue to use them. For many who could not make the transition from COM to the .NET framework this will ultimately be their only course of action. For those who are just starting out in the developer community, I suggest that you not waste your time with pre-.NET versions and go straight into .NET, this way you won't have to un-learn a bunch of bad habits like control arrays and non-OO develpment practices. For those of us who have been with VB for the long haul, if you can make that transition from COM to the .NET framework, I raise my glass to you, it is a considerable leap but one well worth taking.
I enjoy posting in these forums and I enjoy helping young developers begin their walk down that path that, for many, offers a challenging and rewarding career or hobby. I hope that the posts that I have made have truly been benificial. If they have not I will do my utmost to do a better job in the future.
This is a great bunch:thumb:
Let's get straight, CyberHawke.
I how to use .NOT since it's first beta and wasn't then nor I'm now trilled with it. It's ok type language. Point is - it's not Visual Basic anymore (pure java in vb's shell).
Second thing is that I'm in this buisness for about 20-25 years with few breaks at some points and VB is the language of my choice since the beginning. I've seen alot of different tools and let me tell you: VB6 is still the best language out there and it's complitely bizzare to ignore this fact. VB.Not or C# are yet to proove themselves. Control Array is just a small drop in the ocean that MS produces just to make money and nothing more than that. They came out with VC++ and MFC became over the sudden the most powerfull tool labrary, then it was VB5 turn and many forgot C programmers switched to VB due to its simplity coding wise. What we see now is opposite transition - instead of simplifying things MS decides to compicate the hell out it.
Learning curve and everything that comes along are part of any transition so VB.NOT is no different.
I think I'm done with this thread.
Best of luck and Cheers.
Your grasp of the English language is as inspiring as your ability to spell.
Regarding your comment on vb being the greatest language out there, that my friend is opinion and not one widely shared. I love vb, don't get me wrong, but it has a lot of failures and lacks a considerable amount of functionality that is supported by most other languages. VB has been for many years considered a "toy" language by those who coded in much more robust languages such as C++ and PowerBuilder. But that's fine, that "toy" language has netted me many toys over the years, so they can call it what they will, but their reasoning is sound. You just cannot do everything in VB that you can in C, C++ and the like. So calling it the best language is down right laughable. True many C developers made the jump to VB, but only for small applications that were business oriented, ever try to write a device driver in VB? how about a real game like EverQuest or Age Of Mythology? ok, how about something simple like a TCPIP wrapper, I wrote one in VB, but performance was terrible, I and several other developers attempted to make it robust enough for our purposes, but I ultimately resorted to writing it in C++ becuase VB just could not handle the call backs.
Most languages have their purposes, but VB.NET is far and above the old vb. If you have trouble making the transition, Microsoft has provided many wizards to help with doing things like data access and control creation, but what they are trying to do is turn the developer community back into good solid programmers.
btw, I have been programming since 1975, and I can't remember all the languages I've used in that time, but they have all been useful including VB (both COM and .NET).
Cheers
I DON'T care if any of you respond to this thread every 1 minute but it's really not worth it . If your problem has to do with naming convesion that control arrays follow then name it like this(at least it looks better than brakets) :Quote:
Originally posted by RhinoBull
If it bothers you that much - simply don't get involved.
So far all responds were leading toward WORK ARROUNDs especially by CyberHawke. The whole point of having ControlArray is be able to reference group of controls by INDEX and someone's already pointed it out. Instead of such extremly simple way we have to do all that nonsence discussed in this thread and beyond.
Regardless of any inputs, opinions and whatever - Control Array is one very powerfull feature .NOT could have !!!
Don't misinterpret my words next time . I'm one of those whouys appreciate what everyone does here . :)Code:MyControl1.Blah
MyControl2.Blah
MyControl3.Blah
it's a great implementation of the available functionality built into the .NET framework, and is a great work around for lack of true control arrays, nice job Pirate :thumb: