Quote Originally Posted by pacoperez
Hi there! This is Carlos from Spain.

Guess this must be the most talked-about topic in the entire forum, but as long as I'm relatively new at programming I'll just dare to ask.

Is it really worth migrating from VB6 into new .NET?

I've been working with VB6 for several weeks now and although I've developed nothing more than just some pretty simple applications I feel myself quite confortable with the VB6 Integrated Development Environment. I've been able to get pretty used to the VB's graphic environment by now and I don't wish to change just for the sake of it.

Are they very different from each other? Is it for the better?

Should I keep working with VB6 with the view of improving my programming techniques before jumping over to the .NET version or it doesn't really matter at all whether I wait or not?

Any advice will be greatly appreciated.

Also, could anyone tell me where I could get the Smart Menu XP application (if there's any as such)? I just can't find it anywhere in the internet and I can't get the VB standard menus to work with the vbSkinner 2 skins -- which is somewhat frustrating to say the least.

Any alternatives out there maybe? I'd really like to be able to work with menus without having to use the VB standard forms (I'm sorta tired of the WinXP visual look).

Thanks in advance to everybody! Greetings from Spain.

Carlos.
Very simple answer, how many people still cut their grass with scissors ? Heh ... not scissors but those really old grass mulchers (not the lawn mowers). They were very tiresome, most of the time the grass was not cut right, you'd have a lot of missing spots, and you'd be sweating...

So they invented the lawnmower...which I hope everyone is using today...but it doesn't stop there..they came out with the riding mowers and they knocked prices down. You see my point here is the old eventually dies out...even with programming. How many people do you know still program in QBasic or Pascal? Maybe SOME but not many. MS is going to stop supporting VB6. VB6 is not true OOP, there are a lot of blind spots, and cheats people come up with to handle OOP.

Interfacing, structures, inheritance, threading and all that...well they can be hacked and are "sort of" supported but it is painful and a lot of code. I would definately recommend you make hte move to .net. Not only is it a learning experience but the amount of integration with the CLR (Common Language Runtime) far beats any other deal out there.

To be quite honest microsoft's whole philosphy on most of this stuff has changed so that things become well more integrated, more web enabled, more collaborative. Why do you think they made these big changes ? The answer to your question is definately, you should PLAN if not DO change your existing legacy systems.