Why is VB.NET better than VB ?

  • Thread starter Thread starter Guest
  • Start date Start date
Someone asked that a few days ago, look down the posts in this group for a
rather lengthy reply

Regards - OHM#

Dickson said:
Just that.

Regards - OHM# (e-mail address removed)
 
OOP

I find that only something that is needed to handle that much larger
toolbox.

If there was an other way it was for me ok also.
 
Yeah, I can really see him putting that in the business justification case
for his boss, can't you ?

Costs : £10,000

Reason : Someone on the usenet newsgroups told me "It just IS!" better.

LOL

Regards - OHM

Chris said:
On Fri, 12 Dec 2003 05:41:05 -0800, Dickson Woo wrote:

It just IS!

;)

Regards - OHM# (e-mail address removed)
 
Dickson Woo said:
Just that.

Wll, think of it this way... Why is a duck egg nicer than a chicken egg?

1) It's bigger
2) It tastes more "eggy"
3) The shell is harder to break
4) It's got more sulphur in it so you keep more people away when eating
duck egg sandwiches :)
5) They're more expensive

;-)

Lorne
 
I beg to differ. Read my post up above a little bit. In my VB6
program, it took one line of code to do the same thing it takes VB.NET
ten lines of code to do.
 
It must be the Friday madness !

OHM

Lorne said:
Wll, think of it this way... Why is a duck egg nicer than a chicken
egg?

1) It's bigger
2) It tastes more "eggy"
3) The shell is harder to break
4) It's got more sulphur in it so you keep more people away when
eating duck egg sandwiches :)
5) They're more expensive

;-)

Lorne

Regards - OHM# (e-mail address removed)
 
Hi Kevin,

When you want to make a wooden car, you can use a hammer.

But that makes a hammer not the best tool to make a car.

Just a thougth,

Cor
 
Is that why they are bringing out Woodbey, the next generation of VS.

;-)

Regards - OHM#
Hi Kevin,

When you want to make a wooden car, you can use a hammer.

But that makes a hammer not the best tool to make a car.

Just a thougth,

Cor

Regards - OHM# (e-mail address removed)
 
Some Other Reasons:
Microsoft will no longer be developing major versions of VB classic
It appears that future technology trends will be geared towards .NET
e.g. XAML
 
I beg to differ. Read my post up above a little bit. In my VB6
program, it took one line of code to do the same thing it takes VB.NET
ten lines of code to do.

That is not a good argument because the same applies in reverse. There are
things that can be done in VB.Net in one line that takes more lines to do
in VB Classic. There are some things that can be done in VB.Net that
either impossible or very difficult to do in VB Classic (Windows Services
comes to mind).

In any case, use the best tool for the job. If VB Classic is that tool,
then use it. If not, use something else.
 
Well said chris.

Chris Dunaway said:
That is not a good argument because the same applies in reverse. There are
things that can be done in VB.Net in one line that takes more lines to do
in VB Classic. There are some things that can be done in VB.Net that
either impossible or very difficult to do in VB Classic (Windows Services
comes to mind).

In any case, use the best tool for the job. If VB Classic is that tool,
then use it. If not, use something else.


--
Chris

To send me an E-mail, remove the underscores and lunchmeat from my E-Mail
address.
 
As long as I have the attention of all you VB.NET experts, let me ask
the question:

How can I make a textbox control so that the user can't edit the text,
without setting the Enabled property to False (I don't want the
contents greyed out)? I did this in VB6 by putting the textbox in a
frame and then disabling the frame. Can't do that in wonderful .NET...
 
Set readonly to true.


Kevin said:
As long as I have the attention of all you VB.NET experts, let me ask
the question:

How can I make a textbox control so that the user can't edit the text,
without setting the Enabled property to False (I don't want the
contents greyed out)? I did this in VB6 by putting the textbox in a
frame and then disabling the frame. Can't do that in wonderful .NET...
 
I discovered that, but unfortunately it doesn't work with this type of
routine:

For Each Control
If Control is Textbox Then
Control.ReadOnly = True
End If
Next

Or am I missing something?
 
Back
Top