vb6 v.s. vb.net

Hey everyone, I am just wondering if in the long run, it is worth switching from vb6 to .net.

I havnet been programming too long with vb, just a little over a year, but I only recently got a copy of vb6, probably 6 months ago, I have been cheap and was programming through MS Office for awhile since it comes with vb editor, lol, but anyways, I dont know if .net really is all worth it. I know if I stoped using vb6, I would have to learn a lot of different ways .net codes things. I did try .net downloading the free visual basic 2003 express beta, but I didnt like it because it seemed very slugish. I downloaded it on my computer at home, it is a little out dated, it is a p3, 1 ghz, 512mb memory, but I wouldnt consider it slow.

Well what I am trying to get to is when using .net, it starts up a lot slower, which I dont mind at all, but it starts up and runs the applications slower as well.

So, I just wanted to know if anyone could explain to me what makes .net soo much better?

.NET is closer to true Object Orientated Programming. It runs slower on your system because
the Framework requires more resources. No offense but I would definately recommend running
it on a P4 system with at a minimun of a gig of ram.

You can do sooo much more with .NET then you ever could with VB6, with less lines of code too!

Ok, well I guess I should be switching to .net then, and getting a better computer. I just built a new computer but gave it to my girl friend for vday. Its an athlon xp 2700 with a gig of ram, dual ram support, I dont know if it makes a diff or not, i should of kept it for myself =(.
(BTW, athlon is better then pentium =P)

Quote:

---

Originally Posted by RobDog888

.NET is closer to true Object Orientated Programming. It runs slower on your system because
the Framework requires more resources. No offense but I would definately recommend running
it on a P4 system with at a minimun of a gig of ram.

You can do sooo much more with .NET then you ever could with VB6, with less lines of code too!

---

I had to upgrade my box for running the framework. THe framework slowed down my PC considerably. I now have a 512 MB DDRAM on it. However considering hte question of moving to .NET, my suggestion is to avoid it. I have landed myself up in such a project htat involves moving from VB6 2 VB .NET. Also my customer is not interested in spending any more money . I am facing a lot of problems. I am thinking of writing a book. :)

Learning .NET is another issue. From a long term point of view, my suggestion is to learn CSharp.

Best of luck!

Quote:

---

Originally Posted by epod69

Ok, well I guess I should be switching to .net then, and getting a better computer. I just built a new computer but gave it to my girl friend for vday. Its an athlon xp 2700 with a gig of ram, dual ram support, I dont know if it makes a diff or not, i should of kept it for myself =(.
(BTW, athlon is better then pentium =P)

---

Nothin' says lovin' like a shiny new computer ;)

I use an Athlon 1.2Ghz with 256MB RAM as one of my dev machines. The other is a P4 3Ghz with either 512MB or 1GB. I don't see any real difference between the two, so I am surprised that you are finding .NET sluggish.

I loved VB6, and took a long time moving to .NET just because there was a bit of a learning curve (small, but it's real). VB6 did everything I wanted, why should I switch?

I finally took the plunge last summer, and the last time I used VB6 was......last summer! .NET is terrific. I find that I am writing faster than ever before, designing more maintainable code, and have fewer bugs. A great amount of this is due to the IDE, rather than the language itself, but that is a minor point.

Go for it!

You can download the .net sdk for free... a there are about three free IDE's to use with it (none of them fully integerate both web and forms dev - but they can complement one another).

.Net is not sluggish in comparison to vb6. The sluggishness that appears is classes built in .net are normally Just in Time compiled - whereas in vb6 they are compiled in the executable. So the first time the class is called upon, the framework has to compile the class from MSIL.

If you're looking for a job these days - you're gonna need .Net development experience - because everything in the corporate world is being ported over.