By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,192 Members | 1,248 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,192 IT Pros & Developers. It's quick & easy.

Control arrays converted from VB6

P: n/a
In VB6 I made heavy use of control arrays
I see they have been 'deprecated' in vb.Net, with a questionable explanation
that they are no longer necessary which just addresses the event issue!
Problem is I commonly associated several other controls with the same index
inside the event handler - eg a
Directory listbox, Label, Checkbox, Textbox Drivebox etc all associated with
identical index.

Now I see Control arrays belong to VB6 compatibility.

So how in a converted VB6 program can I extend the control arrays at design
time? or run-time for that matter?

I guess VB6 compatibility creates a run-time array of controls with related
type and names - am I right?

So do I need to create a Control object array at form load time, and replace
control references with array references? Is that how VB6 compatibility
does it?

How do other people handle control arrays in .Net

Thanks!
Nov 21 '05 #1
Share this Question
Share on Google+
8 Replies


P: n/a
Sorry - double post due to Outlook-Express reported server error

Nov 21 '05 #2

P: n/a
Greg,

This newsgroups is full of this.

In VBNet has every control an controlcollection. That is as well for the
form itself.

However what you probably need is something as
\\\
dim ctrArray() as Control = Control() {textbox1, textbox2, combobox1, etc}
///
When you use it with a special property/method of a control (not needed for
by instance "name") than you have to do
\\\
If typeof ctr(x) Is combobox then
directcast(ctr,combobox).selectedindex = 1
End it
///
I hope this helps?

Cor
"Greg" <Gr**@discussions.microsoft.com>
In VB6 I made heavy use of control arrays
I see they have been 'deprecated' in vb.Net, with a questionable
explanation
that they are no longer necessary which just addresses the event issue!
Problem is I commonly associated several other controls with the same
index
inside the event handler - eg a
Directory listbox, Label, Checkbox, Textbox Drivebox etc all associated
with
identical index.

Now I see Control arrays belong to VB6 compatibility.

So how in a converted VB6 program can I extend the control arrays at
design
time? or run-time for that matter?

I guess VB6 compatibility creates a run-time array of controls with
related
type and names - am I right?

So do I need to create a Control object array at form load time, and
replace
control references with array references? Is that how VB6 compatibility
does it?

How do other people handle control arrays in .Net

Thanks!

Nov 21 '05 #3

P: n/a
Thanks for your reply - I was hoping to find something to give me DESIGN Time
control arrays; I think Ken Tucker and Herfried Wagner have answered my
question in the double-posted thread; thank you

But it's no surprise that the Group is full of this particular issue! It
was quite a shock to find something so useful and flexible discarded with no
obvious benefit

"Cor Ligthert" wrote:
Greg,

This newsgroups is full of this.

In VBNet has every control an controlcollection. That is as well for the
form itself.

However what you probably need is something as
\\\
dim ctrArray() as Control = Control() {textbox1, textbox2, combobox1, etc}
///
When you use it with a special property/method of a control (not needed for
by instance "name") than you have to do
\\\
If typeof ctr(x) Is combobox then
directcast(ctr,combobox).selectedindex = 1
End it
///
I hope this helps?

Cor
"Greg" <Gr**@discussions.microsoft.com>
In VB6 I made heavy use of control arrays
I see they have been 'deprecated' in vb.Net, with a questionable
explanation
that they are no longer necessary which just addresses the event issue!
Problem is I commonly associated several other controls with the same
index
inside the event handler - eg a
Directory listbox, Label, Checkbox, Textbox Drivebox etc all associated
with
identical index.

Now I see Control arrays belong to VB6 compatibility.

So how in a converted VB6 program can I extend the control arrays at
design
time? or run-time for that matter?

I guess VB6 compatibility creates a run-time array of controls with
related
type and names - am I right?

So do I need to create a Control object array at form load time, and
replace
control references with array references? Is that how VB6 compatibility
does it?

How do other people handle control arrays in .Net

Thanks!


Nov 21 '05 #4

P: n/a
Greg,
But it's no surprise that the Group is full of this particular issue! It
was quite a shock to find something so useful and flexible discarded with
no
obvious benefit

Only from persons who come just from VB6. After a while they don't want that
probably no more because there are so much VBNet methods which give more
control to do what you want, almost endless and when you know them easier to
use.

Cor
Nov 21 '05 #5

P: n/a
"Cor Ligthert" <no************@planet.nl> schrieb:
But it's no surprise that the Group is full of this particular issue! It
was quite a shock to find something so useful and flexible discarded with
no
obvious benefit


Only from persons who come just from VB6. After a while they don't want
that probably no more because there are so much VBNet methods which give
more control to do what you want, almost endless and when you know them
easier to use.


I disagree. Control arrays were one important part of the real RAD
experience of VB Classic, because they provided an easy-to-use design-time
support.

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://dotnet.mvps.org/dotnet/faqs/>

Nov 21 '05 #6

P: n/a
Herfried,

I know that you disagree that, I have often seen that in this newsgroup.

It is often that people love there first programming language they were real
active with and cannot see the worse things of it.

However an advise try to leave that behaviour.

Learn to look at your first programminglanguage even with more distance than
others.

And watch to embrace not directly any marketing message that fits what you
want to see. When others who never used VB6 however are expirienced in VBNet
that it is good, than you have a better measuring point.

And those people are probably even younger than you.

However just an advise feel free to do with it what you want.

Cor

"Herfried K. Wagner [MVP]" <hi***************@gmx.at>
"Cor Ligthert" <no************@planet.nl> schrieb:
But it's no surprise that the Group is full of this particular issue!
It
was quite a shock to find something so useful and flexible discarded
with no
obvious benefit


Only from persons who come just from VB6. After a while they don't want
that probably no more because there are so much VBNet methods which give
more control to do what you want, almost endless and when you know them
easier to use.


I disagree. Control arrays were one important part of the real RAD
experience of VB Classic, because they provided an easy-to-use design-time
support.

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://dotnet.mvps.org/dotnet/faqs/>

Nov 21 '05 #7

P: n/a
"Cor Ligthert" <no************@planet.nl> schrieb:
It is often that people love there first programming language they were
real active with and cannot see the worse things of it.
VB Classic was not my first programming language.
However an advise try to leave that behaviour.


Why? Give me some reasons why control arrays (+ design-time support) are so
bad that I should not use them.

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://dotnet.mvps.org/dotnet/faqs/>

Nov 21 '05 #8

P: n/a
> "Cor Ligthert" <no************@planet.nl> schrieb:
It is often that people love there first programming language they were
real active with and cannot see the worse things of it.


VB Classic was not my first programming language.

I took a long time to describe it the way I did, to avoid this message
however I did not succeed. I know that already, however in my opinion is VB6
the the first you embraced.

:-)
However an advise try to leave that behaviour.


Why? Give me some reasons why control arrays (+ design-time support) are
so bad that I should not use them.


It is not the discussing point, the point is that the ones who want to
discuss this have all a very deep VB6 background. That does not mean I did
not used it, however I am almost forgotten what it was.

The only thing I rembember me is that I first found it sad that the control
array was gone, and now that I have seen so much better aproaches for that
am afraid that it comes back and people start using it again.

I thought to remember me that it was one of my first questions in this
newsgroup which you answered. (Beside that favorites, what still is great,
was it I thought as well one of your last answers on programming questions
from me)

:-).

Cor

Nov 21 '05 #9

This discussion thread is closed

Replies have been disabled for this discussion.