Why did M$ drop componant arrays?? I just don't understand this at all...:eek: :mad: :eek: :mad:
I loved those things.
Printable View
Why did M$ drop componant arrays?? I just don't understand this at all...:eek: :mad: :eek: :mad:
I loved those things.
are you talking about control arrays??? there was really no need for them anymore.. but if you want to learn about ways around them or ways to implement your own.. do a search on just the VB.NET forum for control array and you will find many topicsQuote:
Originally posted by RudyL
Why did M$ drop componant arrays?? I just don't understand this at all...:eek: :mad: :eek: :mad:
I loved those things.
I say componant, you say control.. :DQuote:
Originally posted by kleinma
are you talking about control arrays??? there was really no need for them anymore.. but if you want to learn about ways around them or ways to implement your own.. do a search on just the VB.NET forum for control array and you will find many topics
I will look into that. Thanks :)
If it's any consolation, I was pretty frustrated at them doing away with control arrays as well, but when you do get your head around the .NET way of doing things it's very powerful, and you can do a lot more than you could with control arrays. Though I have to say that there is a lot of legacy stuff that MS ought to have junked before control arrays IMHO.
Hi,
ControlArrays have not been dropped in VB.NET. The name has been dropped because the method of referencing them, using an index number, has been dropped. You can still use an Array of Controls, e.g.
Dim Button(10) As Button
or you can use the Tag property of the control to act in the same way as an index.
MSDN Help gives other options.