Re: VB 6 vs VB.NET
- From: "Robert Conley" <robertsconley@xxxxxxxxx>
- Date: 27 Jan 2007 20:20:45 -0800
On Jan 27, 8:36 am, "jonny" <nelso...@xxxxxxxxxxx> wrote:
1.) My question is will VB 6 code be out dated in near future.
The code will through the lifetime of Vista. New tool development for
VB6 is minimal. And IDE may break in some future version of Vista.
(Mainly because of the security model of Vista)
2.) If I want to be a code writer should l stop spending all my time
learning VB 6 code?
No and yes. You should learn a variety of different languages so can
effectively understand the circumstance each language should be used.
If you are interested in Web programming then your toolset is going to
be different than somebody dealing with embedded machine controllers.
My application is a CAD/CAM program that controls a X-Y metal cutting
machine. It is written in Visual Basic 6, however I have a half dozen
libraries written in C/C++ and one written in Delphi Pascal (a DXF
File Import that we bought the source code too). The machine control
portion of our system requires knowing 8052 assembly language, and CNC
G-Code programming. In addition we have a job costing module that
require coding up SQL to query against database.
So learn as many as you can. I recommend any of the following Visual
Basic, QuickBASIC, C#, Java, Delphi Pascal, 808x assembly language,
lisp, ruby, python, perl, SQL, PHP, and C/C++. If you learn enough
about these to write some basic programming you are on your way to
tackling any programming job.
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.
VB.NET is a basic dialect. While it is still basic it not compatible.
In a practical sense it means that if you have a new project you will
fine that your experience with VB 6 helpful. If you have a existing
project that you want to bring forward VB.NET is a royal pain in the
ass. Drawing and printing are completely different.
Note that in Visual Studio 2005 (not earlier versions) VB.NET can be
used pretty much like in VB 6. This because they finally implemented
edit and continue in VS 2005. THis applies to VB.NET express which is
free.
The biggest difference you will notice is that forms are classes. One
physical file now can have more than one thing in it. Multiple
classes, multiple modules, multiple forms, etc.
4.) What are the advantages of VB.NET? Why is it so hard to convert my
VB 6 code over to VB.NET.
#1 reason is because the VB.NET team was drawn from the dotNET/C# team
and had no training or appreciation of the history of Visual Basic.
#2 .NET was new. The tricks of compiliing to IL (the assembly language
of .NET) haven't sunk. In a nutshell the .NET runtime is pretty
flexible and a variety of languages can be adapted to use it. But MS
was so focused on C# that everything they made in the intial version
worked like C# with different syntax.
VB.NET today has a lot of nice features with advanced languages
features first class access to the .NET framework. Writing a project
in VB.NET can save a lot of coding if designed right.
Plus there is Mono which is an open source implementation of the .NET
runtime and framework.
5.) Also, I just wanted to see what some of the code writers are
saying about VB.NET vs VB 6.0
They drank the leftover Kool-Aid from Jonestown with the utter lack of
backwards compatibility with VB.NET. If it wasn't for Mono I would not
consider using .NET. Plus I caution any programmer using a Microsoft
only solution. They can't be depended to maintain any of their code
base. This company threw away the largest group of programmers when
they created VB.NET.
Rob Conley
.
- References:
- VB 6 vs VB.NET
- From: jonny
- VB 6 vs VB.NET
- Prev by Date: Listview flashing screen
- Next by Date: Re: Form.Caption
- Previous by thread: Re: VB 6 vs VB.NET
- Next by thread: Re: VB 6 vs VB.NET
- Index(es):
Relevant Pages
|
Loading