VB6 or VB.NET

Hi there,

I'm confused ;(

- I just formated my PC and I want to install VB on it.
- My PC is WIN XP Professional PIII 750MHz 256MB 20GB.
- I have experience background in VB6 coding.
- I have VB.NET Professional 2003 CD
- I have VB 6 Enterprise CD

I have some question:

Q1. Is it diffecult to code in VB.NET when I have VB6 background?
Q2. Do you suggest leaving VB6 and go for VB.NET? (some collegues didn't agree!)
Q3. What is the deiffernces between VB6 Enterprise and Profissional ediotions? and which one is better?
Q4. Will it slow down my PC if I install both VB6 and VB.NET?
Q5. Is it difficult to install VB .NET? (I have 16 CDs

P L E A S E 5 Q U E S T I O N S N E E D 5 A N S W E R S

Please help guys

You could check out this site for lots of information

http://msdn.microsoft.com/vstudio/

Please refrain from the ALL CAPS comments. It is considered screaming and is rude.

VB6 is quite different from VB.Net. You can transfere projects (one way) from VB6 to .Net but not everything may transfere correctly and a lot of things have changed between the two version.
Do I suggest going to .net? It would probably be worth while to learn, but I wouldn't abandon VB6 either. .net is still in its infancy and isn't in such widespread use as VB6 currently is. Pretty much, don't abandon any language you learn.
Enterprise vs Professional: enterprise comes with some extra tools and what-nots. Which one is better? Depends on what tool you need. Professional suites most developers imho.
4 & 5? Don't know.

as far as your last two questions, als -

No, it should not slow down your PC to install both .NET and VB/VS6 (unless you have an unusual condition, like low disk space and you run out of swap space). VB6 and .NET use different compilers (the VB "Ruby" engine and the CLR, respectively), and will run side-by-side when a VB app is called in both architectures.

No, the .NET framework is not difficult to install, it's just a little time consuming... especially if you're installing the entire MSDN library along with it.

I have just made the transition to .NET from several years of VB6 programming experience, and I can tell you that it's not that hard of a change. There are a few changes to try and bring VB closer to C++ as far as implementation goes, but it's nothing that very hard to understand. I will tell you this, though. I have applications that I will most likely never convert to .NET due to their complexity, and as such, am keeping up my VB6 skills on debugging and enhancements.