Re: VB.net vs VB 6.0

Tech-Archive recommends: Fix windows errors by optimizing your registry

Brad,



We have a very large code base in VB6 and have a nearly finished project in
Asp.Net.



> There appears to be a huge learning curve for .net.



There is, but it is not insurmountable, and .net has a lot of new and
interesting ideas.



> Is moving to .net really going to buy us anything down the road?



Well, if you're not planning on retiring soon. The problem with VB6 is that
it's great today, but sooner or later it is going to wear out.



> Should we even bother looking at it or should we stay with version 6?



For new development, I would definitely suggest looking at it. If you have a
large code base that you want to conserve, I would suggest sticking with
VB6. Except for the Asp.Net project we are doing, all the rest of our
development work is in VB6. Porting our apps at present is out of the
question.



>Is it buggy?



It's not bad. I've worked with much worse.



> How well does it perform? The design interface sure seems sluggish...



The design interface crawls like a snail, but once you've got your program
up and running it's not bad. It is different from VB6 though. Some things in
Vb.Net are slower than VB6 (like Mid$, binary file access), but once you
adjust to the .net philosophy and code to be fast in .net, it's ok. One
thing that really is lacking is edit and continue (promised in VS2005).
Every time you have to stop to modify something, the behemoth has to stop
rolling, you change a line of code, hit F5 and the behemoth tries to get up
on its feet again.



> Are there any horror storys with .net?



Not that I know of, except for those who have attempted porting a large VB6
program.



> Is VB 6 going to continue to be supported by Micorosoft for a while ?



No way.


> We are just unsure exactly what to do...

Join the group.



Gary


.

Relevant Pages

  • Re: Is VB6 still alive and well?
    ... If there was a way we could move our huge code base ... But I too have an installed VB6 code base and have yet to see the ... VB6 apps will probably continue to work fine for many years but that I ... Peter Aitken ...
    (microsoft.public.vb.general.discussion)
  • Re: Is VB6 still alive and well?
    ... If there was a way we could move our huge code base ... >>>have sympathy for those of us who have a lot more worries on our ... > is doing anything to cause problems with VB6 apps down the road. ... > VB6 apps will probably continue to work fine for many years but that I ...
    (microsoft.public.vb.general.discussion)
  • Re: Is VB6 still alive and well?
    ... Peter, without wishing to get into an argument on this subject, I feel your ... If there was a way we could move our huge code base ... than simply 'which language do I like best'. ... >> I am still using VB6, I guess I am very behind the time. ...
    (microsoft.public.vb.general.discussion)
  • Re: Going back to VB 6.0 Cant get help here.
    ... > people in the VB 6.0 newsgroup answer without throwing in an insult. ... Since the code's basically unchanged from VB4-32 through VB6, ... years before that kind of code base is built in any version of .Net (and, ... groups if you post .Net questions there;-) ...
    (microsoft.public.dotnet.languages.vb)