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

VB6 vs VB.NET

P: n/a
I was hoping to start up a discussion on the pros and cons of VB6 vs
VB.NET. Specifically, why should someone switch from VB6 to VB.NET? On
the other hand, why should someone not use VB.NET (besides learning
curve which is my current reason)?

David
Jul 17 '05 #1
Share this Question
Share on Google+
12 Replies


P: n/a
On 11 Aug 2004 08:15:08 -0700, dh*******@chestnut.org (David) wrote:
I was hoping to start up a discussion on the pros and cons of VB6 vs
VB.NET. Specifically, why should someone switch from VB6 to VB.NET? On
the other hand, why should someone not use VB.NET (besides learning
curve which is my current reason)?


Well, since we're mostly pre-.Net here, I'd have to say you're mostly
going to get cons, rather than pros.

....wait a minute, that doesn't sound right...

[ahem] Let's try that again... I, personally, have tried VB.Net and
don't like it. Some people say it's a "natural upgrade" to VB6, to
which I say nuts. VB.Net is a totally different language; it doesn't
work the same as "regular" VB.

The biggest advantage that I can see is that Microsoft will support
VB.Net for some time to come, while they're phasing out their pre-.Net
languages. Also, in theory the .Net framework can be built for
multiple platforms (and there are projects underway) allowing for
portability - similar to Java's VM.

A couple disadvantages I can think of right off-hand:
- relies on the .Net framework
- relatively easy to reconstruct something resembling the original
source code from the compiled program

Now, if you want some people to give you reasons to switch to .Net, go
to this group and ask there:
news:microsoft.public.dotnet.languages.vb
Jul 17 '05 #2

P: n/a
I have to give another point of view. I am self taught, starting with
Basic on a TI994a computer (remember these?), then the obvious
Q-Basic. My first VB version was 4, I now have VB6sp6 and VB.Net
2003, and 2005 beta.

Using VB.Net was wierd at first, I guess because I was used to VB6.
After using it for a while (a few months) I really like it.
Everything I do now I do in VB.Net. I am not a full time programmer,
so you may get different opinions on this. I have done a lot of
programming for companies, and still support 3 apps I wrote in VB6.

After using VB.Net, I have to say I wish I had it when these apps were
written. VB.Net is a more powerful language then VB6. Going back and
modifying the apps I still support, I notice things that could have
been done a lot easier in VB.Net.

As far as depending on the 1.1 Framework (2.0 for VB.Net 2005), that
is true. You need that installed to run the VB.Net programs. On the
flip side, most OS's will have this installed already. It comes with
WinXP, and 2003 Server, so there will not be a great disadvantage to
requiring this.

Yes, I know there are still a lot of 98, NT, and 2k machines out
there, that is why I still need VB6

Hope this helps!

On 11 Aug 2004 08:15:08 -0700, dh*******@chestnut.org (David) wrote:
I was hoping to start up a discussion on the pros and cons of VB6 vs
VB.NET. Specifically, why should someone switch from VB6 to VB.NET? On
the other hand, why should someone not use VB.NET (besides learning
curve which is my current reason)?

David


Jul 17 '05 #3

P: n/a
> I have to give another point of view. I am self taught,
starting with Basic on a TI994a computer (remember
these?),


Yes... not only do I remember them, I started on the TI99/4 too! (Note,
no "a", although I eventually had one of those also.) Did you ever
happen to come across either of these programs, TI-Asteroids or Shuttle
Command, in your TI travels?

Rick

Jul 17 '05 #4

P: n/a
Yeah, I remember Shuttle Command, but not asteroids. I remember when
I got the Extended Basic cartridge - I thought "This computer can do
ANYTHING!" How times change... I never got the expansion box, so I
never worked up to getting a floppy drive - everything saved on a
cassette tape.

On Wed, 11 Aug 2004 22:02:25 -0400, "Rick Rothstein"
<ri************@NOSPAMcomcast.net> wrote:
I have to give another point of view. I am self taught,
starting with Basic on a TI994a computer (remember
these?),


Yes... not only do I remember them, I started on the TI99/4 too! (Note,
no "a", although I eventually had one of those also.) Did you ever
happen to come across either of these programs, TI-Asteroids or Shuttle
Command, in your TI travels?

Rick


Jul 17 '05 #5

P: n/a
> Yeah, I remember Shuttle Command, but not asteroids.

I was the programmer for both of those programs. I hope you enjoyed
Shuttle Command... if you had a legitimate copy that is.<g>

I remember when I got the Extended Basic cartridge -
I thought "This computer can do ANYTHING!"
That was exactly how I felt.

How times change... I never got the expansion box, so I
never worked up to getting a floppy drive...
I had one... single-sided, single-density... a whole 90K of storage!

....everything saved on a cassette tape.


Weren't those things fun? Three-minutes of continual screechy chatter
just to load one program! The floppy was not too much better,
speed-wise; I think it took about a minute to load the same program it
took three-minutes to load by tape.
Rick - MVP

Jul 17 '05 #6

P: n/a
Besides OS, is there another reason why you would stay with VB6? The
..NET framework can be installed on the other operating systems,
correct?

David

Eddie B <> wrote in message news:<4v********************************@4ax.com>. ..
I have to give another point of view. I am self taught, starting with
Basic on a TI994a computer (remember these?), then the obvious
Q-Basic. My first VB version was 4, I now have VB6sp6 and VB.Net
2003, and 2005 beta.

Using VB.Net was wierd at first, I guess because I was used to VB6.
After using it for a while (a few months) I really like it.
Everything I do now I do in VB.Net. I am not a full time programmer,
so you may get different opinions on this. I have done a lot of
programming for companies, and still support 3 apps I wrote in VB6.

After using VB.Net, I have to say I wish I had it when these apps were
written. VB.Net is a more powerful language then VB6. Going back and
modifying the apps I still support, I notice things that could have
been done a lot easier in VB.Net.

As far as depending on the 1.1 Framework (2.0 for VB.Net 2005), that
is true. You need that installed to run the VB.Net programs. On the
flip side, most OS's will have this installed already. It comes with
WinXP, and 2003 Server, so there will not be a great disadvantage to
requiring this.

Yes, I know there are still a lot of 98, NT, and 2k machines out
there, that is why I still need VB6

Hope this helps!

On 11 Aug 2004 08:15:08 -0700, dh*******@chestnut.org (David) wrote:
I was hoping to start up a discussion on the pros and cons of VB6 vs
VB.NET. Specifically, why should someone switch from VB6 to VB.NET? On
the other hand, why should someone not use VB.NET (besides learning
curve which is my current reason)?

David

Jul 17 '05 #7

P: n/a
I did just notice one of the differences, both a pro and a con.

Pro: compilation errors are easier to locate and fix. In VB6, if there
are multiple errors, it will stop at the first one and bring you to
that line. In .NET, it will list them all out for you and let you just
double click the problem line and be brought to that point in the
code.

Con: More coding is needed when using ADO and simple I/O. In VB6, I
could assign a value like strFirstName = rs!FirstName. In .NET, I had
to do strFirstName = rs.Fields("FirstName").Value. I could not even
get away with rs("FirstName"). Similarly, to open a file and print to
it, in VB6 I could just write:

Open "C:\Temp\temp.txt" for Output as 1
Print #1, "Test"

is now

Microsoft.VisualBasic.FileOpen(1, "C:\Temp\temp.txt", OpenMode.Output)
Microsoft.VisualBasic.Print(1, "Test")
David

dh*******@chestnut.org (David) wrote in message news:<83**************************@posting.google. com>...
I was hoping to start up a discussion on the pros and cons of VB6 vs
VB.NET. Specifically, why should someone switch from VB6 to VB.NET? On
the other hand, why should someone not use VB.NET (besides learning
curve which is my current reason)?

David

Jul 17 '05 #8

P: n/a
Yes, it can be installed on other OS's, but it is about 35 megs. This
may not be a problem, but then again...

On 12 Aug 2004 06:35:12 -0700, dh*******@chestnut.org (David) wrote:
Besides OS, is there another reason why you would stay with VB6? The
.NET framework can be installed on the other operating systems,
correct?

David

Eddie B <> wrote in message news:<4v********************************@4ax.com>. ..
I have to give another point of view. I am self taught, starting with
Basic on a TI994a computer (remember these?), then the obvious
Q-Basic. My first VB version was 4, I now have VB6sp6 and VB.Net
2003, and 2005 beta.

Using VB.Net was wierd at first, I guess because I was used to VB6.
After using it for a while (a few months) I really like it.
Everything I do now I do in VB.Net. I am not a full time programmer,
so you may get different opinions on this. I have done a lot of
programming for companies, and still support 3 apps I wrote in VB6.

After using VB.Net, I have to say I wish I had it when these apps were
written. VB.Net is a more powerful language then VB6. Going back and
modifying the apps I still support, I notice things that could have
been done a lot easier in VB.Net.

As far as depending on the 1.1 Framework (2.0 for VB.Net 2005), that
is true. You need that installed to run the VB.Net programs. On the
flip side, most OS's will have this installed already. It comes with
WinXP, and 2003 Server, so there will not be a great disadvantage to
requiring this.

Yes, I know there are still a lot of 98, NT, and 2k machines out
there, that is why I still need VB6

Hope this helps!

On 11 Aug 2004 08:15:08 -0700, dh*******@chestnut.org (David) wrote:
>I was hoping to start up a discussion on the pros and cons of VB6 vs
>VB.NET. Specifically, why should someone switch from VB6 to VB.NET? On
>the other hand, why should someone not use VB.NET (besides learning
>curve which is my current reason)?
>
>David


Jul 17 '05 #9

P: n/a
it will list them all out for you and let you just
double click the problem line and be brought to that point in the
code.
Very true, also, you can assign points of code through this window, if
you are working on something, and want to mark it - do it here. That
way it is easier to find later.
Con: More coding is needed when using ADO and simple I/O. Actually, this is also a Pro. As far as simple text I/O, it is
actually not any harder, plus it allows more freedom to do some things
that were harder in VB6. I have an INI dll that makes writing to and
reading from an ini file kinda like getting a field in a database. In
VB6, you had to read the whole file, in VB.Net you get just what you
want.

As far as ADO, I used to agree. This was one of the big turn-offs for
me in VB.Net. After you get used to it, it is pretty easy. Have you
used a dataset yet? Sorting and filtering is easier also, do to the
fact that you can write SQL statements for all searches. You can also
join tables - another big plus in my book.

On 12 Aug 2004 15:02:34 -0700, dh*******@chestnut.org (David) wrote:
I did just notice one of the differences, both a pro and a con.

Pro: compilation errors are easier to locate and fix. In VB6, if there
are multiple errors, it will stop at the first one and bring you to
that line. In .NET, it will list them all out for you and let you just
double click the problem line and be brought to that point in the
code.

Con: More coding is needed when using ADO and simple I/O. In VB6, I
could assign a value like strFirstName = rs!FirstName. In .NET, I had
to do strFirstName = rs.Fields("FirstName").Value. I could not even
get away with rs("FirstName"). Similarly, to open a file and print to
it, in VB6 I could just write:

Open "C:\Temp\temp.txt" for Output as 1
Print #1, "Test"

is now

Microsoft.VisualBasic.FileOpen(1, "C:\Temp\temp.txt", OpenMode.Output)
Microsoft.VisualBasic.Print(1, "Test")
David

dh*******@chestnut.org (David) wrote in message news:<83**************************@posting.google. com>...
I was hoping to start up a discussion on the pros and cons of VB6 vs
VB.NET. Specifically, why should someone switch from VB6 to VB.NET? On
the other hand, why should someone not use VB.NET (besides learning
curve which is my current reason)?

David


Jul 17 '05 #10

P: n/a
This would sound like a con to me.

David
Eddie B <> wrote in message news:<5i********************************@4ax.com>. ..
Yes, it can be installed on other OS's, but it is about 35 megs. This
may not be a problem, but then again...

On 12 Aug 2004 06:35:12 -0700, dh*******@chestnut.org (David) wrote:
Besides OS, is there another reason why you would stay with VB6? The
.NET framework can be installed on the other operating systems,
correct?

David

Eddie B <> wrote in message news:<4v********************************@4ax.com>. ..
I have to give another point of view. I am self taught, starting with
Basic on a TI994a computer (remember these?), then the obvious
Q-Basic. My first VB version was 4, I now have VB6sp6 and VB.Net
2003, and 2005 beta.

Using VB.Net was wierd at first, I guess because I was used to VB6.
After using it for a while (a few months) I really like it.
Everything I do now I do in VB.Net. I am not a full time programmer,
so you may get different opinions on this. I have done a lot of
programming for companies, and still support 3 apps I wrote in VB6.

After using VB.Net, I have to say I wish I had it when these apps were
written. VB.Net is a more powerful language then VB6. Going back and
modifying the apps I still support, I notice things that could have
been done a lot easier in VB.Net.

As far as depending on the 1.1 Framework (2.0 for VB.Net 2005), that
is true. You need that installed to run the VB.Net programs. On the
flip side, most OS's will have this installed already. It comes with
WinXP, and 2003 Server, so there will not be a great disadvantage to
requiring this.

Yes, I know there are still a lot of 98, NT, and 2k machines out
there, that is why I still need VB6

Hope this helps!

On 11 Aug 2004 08:15:08 -0700, dh*******@chestnut.org (David) wrote:

>I was hoping to start up a discussion on the pros and cons of VB6 vs
>VB.NET. Specifically, why should someone switch from VB6 to VB.NET? On
>the other hand, why should someone not use VB.NET (besides learning
>curve which is my current reason)?
>
>David

Jul 17 '05 #11

P: n/a
why would they not want to use VB6
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.732 / Virus Database: 486 - Release Date: 7/29/2004
Jul 17 '05 #12

P: n/a
Who would 'they' be? Not sure who this message is directed to...

On Mon, 16 Aug 2004 19:54:58 -0400, "Hal Rosser"
<hm******@bellsouth.net> wrote:
why would they not want to use VB6
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.732 / Virus Database: 486 - Release Date: 7/29/2004


Jul 17 '05 #13

This discussion thread is closed

Replies have been disabled for this discussion.