Re: VB.net vs VB 6.0

Just got back from an MSDN event. VS2005 will probably make you want to move
to .Net. The next version of Web Services and "ClickOnce" features make
seamless deployment and online updating a breeze. The new IDE also adds some
nice touches to development. While I blast Microsoft for something about
once a week, in the case of the IDE, they seem to be on the right track,
motivated to get the developer tools right.

You may however wish to move directly to C# instead of VB.Net. Functionally,
they are nearly identical, but the woefully misguided naming of "VB.Net"
(which has very little to do with "Classic VB") will almost undoubtedly
spell its eventual demise.

"Brad Pears" <donotreply@xxxxxxxxxxx> wrote in message
news:un3$wSVYFHA.3032@xxxxxxxxxxxxxxxxxxxxxxx
> We are a small shop - two IT people. We both are developers etc....
>
> We currently have a mix of VB 6.0 and Access 2000 apps. We are trying to
> develop a strategy for further new development (in in some cases rebuild
> the Access stuff)and basically have decided on either of VB 6.0 or VB .net
> as the standard.
>
> Since neither of us really have much experience with VB .net, would anyone
> out there who does, have any suggestions for us as far as which way we
> should go? There appears to be a huge learning curve for .net. Is moving
> to .net really going to buy us anything down the road? Should we even
> bother looking at it or should we stay with version 6? Is it buggy? How
> well does it perform? The design interface sure seems sluggish...
>
> Are there any horror storys with .net? Is VB 6 going to continue to be
> supported by Micorosoft for a while ?
>
> We are just unsure exactly what to do...
>
> Any comments, tips woudl be greatly appreciated!
>
> Thanks,
>
> Brad
>


.