Re: VB6 vs VB .Net
From: JohnK (johnk_at_nomailback.com)
Date: 02/27/04
- Next message: J French: "Re: Problems with shelled VB app"
- Previous message: JohnK: "Re: Listbox search"
- In reply to: Jim Carlock: "Re: VB6 vs VB .Net"
- Next in thread: Ravichandran J.V.: "Re: VB6 vs VB .Net"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 27 Feb 2004 09:42:54 +0100
Yeah,
I worked many years ago in assembler language... Glad it's over now. You can
produce perfect short code, but one little tiny mistake....
I'll go for VB (6 or .net) and C (whatever dialect) nowadays. I also
programmed many business programs in Cobol, but you wouldn't do that on a pc
now. I know there is even Visual Cobol: argh, I dislike it.
John
"Jim Carlock" <anonymous@10.10.com> schreef in bericht
news:uCPj2TM$DHA.1036@TK2MSFTNGP10.phx.gbl...
> I still think the best programs are the assembly language programs.
>
> There are some nice Windows Assembly language programs
> available today. If you know API, the transition to the assembler
> isn't too bad.
>
> www.masm32.com
>
> --
> Jim Carlock
> http://www.microcosmotalk.com/
> Post replies to the newsgroup.
>
>
> "JohnK" <johnk@nomailback.com> wrote in message
> news:403e73ca$0$12849$3a628fcd@reader1.nntp.hccnet.nl...
> Bill,
> You're making a good point. I agree that new programming must be done in
> VB.NET instead of VB6, but only if the programmer really understands the
> differences between the two products.
> Second, when you want to develop in VB.NET, you can't do it on a W98
> installartion. You'll need at least W2000 or XP, with enough memory inside
> your pc, say 512 Mb to 1024Mb (1Gb) and that's just a part of it. So when
> you make nice VB stuff now on your 128Mb pc with W98, keep on doing that,
> but when you own a > 2Ghz 512Mb machine or more, switch to VB.NET and buy
a
> good book about it, like the VB.NET Bible.
> All differences are explained to you and porting VB6 to VB.NET will not be
> too difficult.
>
> John
>
>
> "Bill McCarthy nospam >" <bill_mcc@<iprimus.com.au> schreef in bericht
> news:OdoFTIF$DHA.1036@TK2MSFTNGP10.phx.gbl...
> > Hi Ian,
> >
> >
> > "Ian Bayly" <ianbayly@paradise.net.nz> wrote in message
> > news:%23shyoi1%23DHA.3816@TK2MSFTNGP09.phx.gbl...
> > > As a long time user of VB (I actually have manuals which came with VB
in
> > > those days), those that know more about these things than I do, tell
me
> I
> > > should upgrade from VB6 to VB .Net.
> > > I have no interest or need to be involved with any web applications.
> > >
> > > Should I upgrade Yes/No?
> > >
> >
> > I think if you are writing new apps, you should definably consider
moving
> to
> > VB.NET. If you decide to stick with VB6 for a while longer, you should
at
> > least consider the potential move and try to factor your code around
> > potential moves later. So at a minimum, you should look at what is
> > involved, and using the VB6 code advisor.
> >
> > As to the actual decision to use VB6 or VB.NET, I personally believe you
> > should base that on technical issues ;)
> > I've read some of this thread, and unfortunately you already have people
> > trying to scare you away from VB.NET, claiming it *might* change in the
> > future. What they are actually doing is try to convince you in one
> > direction based on fear of the uncertainty the future may or may not
> bring,
> > aka FUD ;) Other's have expressed different POV's from me, but have
> focused
> > on the facts, the technical issues.
> >
> > All FUD aside, I think you will in fact find VB.NET is as stable, if not
> > even more so than any other .NET language. MS has invested heavily in
it,
> > with real features such as the first .NET language to have true edit and
> > continue. So realistically, if you decide to go with .NET, and you have
> VB
> > skills, I think you will find VB.NET is the correct choice that will
feel
> > more natural when you use it. Personally, I am also a long time VB
user,
> > and I much prefer the development experience in Vb.NET compared to VB6,
> > partially due to the IDE, but also due to the improved language
features.
> I
> > also find the .NET IDE experience far more productive.
> >
> > Some things you need to consider first are your development environment
> and
> > your client requirements. VS.NET is a real memory hog. To use it, it
> > really works best with a good machine and at least 512 MB RAM. Kind of
> > standard for a brand new machine, but higher end specs for any machine
> more
> > than a couple of years old.
> > On the client side of things, especially as it sounds like you will be
> doing
> > WinForms kind of applications, you really need to consider the client
> > hardware too. The client has to have win98 or later. (no win95). And
> > winforms does have a large footprint. I personally say for .NET, the
> > client's hardware has to be of this century, and that is a pretty good
> rule
> > of thumb. Seriously, on older machines, the initial load time for a
form
> is
> > too much in the eyes of many folk, including mine ;)
> >
> > If your clients and your development environment meet those
requirements,
> > and especially if it is new code, I would definitely go with VB.NET over
> > VB6. For you however, there will be another hurdle, that will be
learning
> > Vb.NET. although a lot of the language is the same, especially in
general
> > look and feel, there's a lot more new features, a lot more new
> > functionality, and a huge set of libraries the .NET framework exposes.
> > The benefits though, include ease of multi-threading, inheritance, more
> > flexible interface mapping, to name just a few. Extending controls is
> > easier, there's xcopy deployment even when using third party controls
etc.
> > Data access uses a disconnected model (which has pros and cons of it's
> own).
> > I think one of my favourite features in winForms, is the ability to
> override
> > the WndProc when writing custom controls. Drawing is way more powerful,
> but
> > also a lot more to learn. (all the newish GDI+ libraries) And if you
> decide
> > later to integrate web services, well it really is easy.
> >
> > Personally, I really do prefer to use Vb.NET compared to VB6, but for
you,
> I
> > think you may face a period of having to learn the new IDE, and all the
> new
> > language features, so for a time, you will be more productive in VB6.
> Long
> > term, and especially if you want to work with SQL Yukon's new features,
or
> > with Windows Longhorn's new features, you will have to move into .NET
> > managed code.
> >
> > But in anycase, weigh up your decision based on technical information,
not
> > on FUD some folk try to persuade people with. And you might also want
to
> > post this question to the microsoft.public.dotnet.languages.vb
newsgroup,
> as
> > there are actually more people in that group than here, so you will get
a
> > response potentially from a wider group. Most of those folk are from a
VB
> > background too.
> >
> > All the best,
> >
> > Bill.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
>
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.580 / Virus Database: 367 - Release Date: 6-2-2004
>
>
>
--- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.596 / Virus Database: 379 - Release Date: 26-2-2004
- Next message: J French: "Re: Problems with shelled VB app"
- Previous message: JohnK: "Re: Listbox search"
- In reply to: Jim Carlock: "Re: VB6 vs VB .Net"
- Next in thread: Ravichandran J.V.: "Re: VB6 vs VB .Net"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
