why should i move vb6 to vb.net

[Peon]

It may sound rude .. 'persuade me'

but i am asking politely to gain better info .. that why should i move or adapt vb.net from vb6. vb6 is doing very well for my projects.

I want get some points which can show me what is plus plus in vb.net which vb6 doesn't has.

Thank You.

[RobDog888]

There are allot of VB6/VB.NET comparison threads already. A quick search will give you many more reasons to switch, but switch is usually the best decision.

[jmcilhinney]

What do you want to do that VB6 can't do or can't do easily? There are already many threads dedicated to which is better and why and I don't think another is required. The simple fact is that if you're happy with VB6 and it can do everything that you need and want to do then there's no point changing.

[Krenshau]

I like using .NET 2.0 because I don't have to write modules just for API calls. I like that it makes moving data across a network easier. I like it more for a lot of reasons, but no one can convince you to switch. That is something you will have to decide for yourself. Eventually, unmanaged code in the higher level languages will probably be very restricted on new operating systems, which can make customers unhappy. I think eventually there will be no choice. It just comes down to whether you want to learn now while everyone is still learning, or later, when your competition is already programming in .NET proficiently.

[Peon]

Actually i am confused because .Net changes and VS also changes but vb6 remains same so its bit easy to go smoothly with vb6.

[Atheist]

I changed from VB6 to VB .Net a year ago, and I'd never go back. I love it all.
Good things:
- Warnings in code (2005)
- Lovely intellisense
- Many easily used classes to do a little bit of everything.
...And many more, just woke up so brain not working at full speed yet..