Re: VB 6 vs VB.NET
- From: Paul Clement <UseAdddressAtEndofMessage@xxxxxxxxxxxxxx>
- Date: Mon, 29 Jan 2007 12:52:26 -0600
On 27 Jan 2007 05:36:39 -0800, "jonny" <nelsonj4@xxxxxxxxxxx> wrote:
¤ I wrote a program using VB 6 and was wondering if the code will be
¤ outdated in near future. I tried to covert my VB 6 code to VB.NET and
¤ it was unless debugging so I finally gave up.
¤
¤ 1.) My question is will VB 6 code be out dated in near future.
I guess it depends upon what you mean by outdated. It continues to run under Vista, although there
may not be full support for all of your application features. It's limited by its existing
capabilities as no new features will be added or existing bugs or incompatibilities fixed.
¤ 2.) If I want to be a code writer should l stop spending all my time
¤ learning VB 6 code?
Yes. Either consider moving on to Visual Basic 2005 or another programming language.
¤ 3.) Write now I am spending a lot of time learning VB 6 code and want
¤ to know if I am waisting my time if the VB 6 code is going to be
¤ absolete and going to VB.NET.
You can carry some of your knowledge of Visual Basic 6.0 to 2005, but many of the development
libraries are either new or different. For that reason I wouldn't spend too much time *learning*
Visual Basic 6.0.
¤ 4.) What are the advantages of VB.NET? Why is it so hard to convert my
¤ VB 6 code over to VB.NET.
The .NET Framework changes, or renders obsolete, some of the functionality that was present in
Classic Visual Basic. While much of the core language is familiar and still present, some of it is
no longer supported. You must learn new features in the .NET Framework in order to work with Visual
Basic 2005.
However, once you learn Visual Basic 2005 and some of the more commonly used .NET Framework
libraries it's so much easier to develop an application in .NET.
¤ 5.) Also, I just wanted to see what some of the code writers are
¤ saying about VB.NET vs VB 6.0
Most of the responses here toward .NET will be negative since this is a Classic Visual Basic
newsgroup, and a lot of folks are rather passionate about the issues caused by the changes in the
..NET version of Visual Basic.
I still use both, primarily because I still have to support applications or COM components developed
in Classic Visual Basic. However, any new applications are developed in Visual Studio 2005.
Paul
~~~~
Microsoft MVP (Visual Basic)
.
- Follow-Ups:
- Re: VB 6 vs VB.NET
- From: jonny
- Re: VB 6 vs VB.NET
- References:
- VB 6 vs VB.NET
- From: jonny
- VB 6 vs VB.NET
- Prev by Date: movie as desktop wallpaper
- Next by Date: Re: Recommended Voice Modem for TAPI
- Previous by thread: Re: VB 6 vs VB.NET
- Next by thread: Re: VB 6 vs VB.NET
- Index(es):
Relevant Pages
|
