Moving from VB6 to dot net

From: aaj (a.b_at_c.com)
Date: 09/27/04 

Date: Mon, 27 Sep 2004 14:25:54 +0100

Hi all

Would anyone be able to offer any unbiased thoughts or advice on reasons to
switch to .Net. I have read some of the literature and read other stuff on
google, but a so much of it seems to be wrapped up in marketing speak I'm
not sure I fully understand what it actually does better.

So before we move from VB6 to DOT NET, I am trying to weigh up the pro's and
cons of each. The stuff we use VB6 for is pretty simple compared to what
most of you guys do, but that said, its still important to us.

Typically most of the software in the company has been written by me in VB6
, and are generally relatively simple standalone packages, stuff like
invoicing software that integrates into our master database, software that
takes information for many different formats, assembles it and then uploads
to the central database etc. My colleague then writes the web stuff using
dreamweaver to view the collated data.

The advantages as I see it for sticking with VB6 are

In general I find it extremely easy and quick to develop with.(see comment
below about database front ends though)
It has always been able to do what I need it to. I have never had a problem
that I haven't been able to work around one way or another
It has been extremely reliable - I can't ever remember either VB6 or the
EXE's I've written and its compiled crashing out

The disadvantages of VB6 are
As far as I see, every one will be using dot net, and I don't want to be
left behind.
Although VB6 is quick and easy to develop with, for database front ends its
still not a patch on using Access front ends and VBA to a sql server
database.

So what I am asking is there any one in a similar position to me, writing
simple software for a smallish company, who made the switch, if so how easy
was it, Is it difficult to switch to a truly object orientated language,
what do you do better now than you did before.. etc

In effect, all though I want to make the move, I would like to justify my
decisions by understanding what are the real measurable reasons for making
the switch and for the simple software we write is it worth the change?

many thanks for any advice

Andy

Relevant Pages

  • Re: Moving from VB6 to dot net
    ... what other advantages does VB dot net have. ... How difficult is it to switch to an object orientated language, ... and then VB6, but the stuff I write tends to be more function ... > to the central database etc. ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Moving from VB6 to dot net
    ... I treat dotnet as another tool rather than ... of vb6 compared to dotnet. ... > to the central database etc. ... > simple software for a smallish company, who made the switch, if so how ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Moving from VB6 to dot net
    ... If all you are writing is simple desktop apps that integrate with a database ... I program in Dot Net and VB6 and can say ... > simple software for a smallish company, who made the switch, if so how ...
    (microsoft.public.dotnet.languages.vb)
  • Re: CallByName in VB.NET...
    ... There are reasons they have not made the switch. ... But no genuine legitimate reasons. ... > already in place written in VB6 that they either need to maintain ...
    (microsoft.public.vb.general.discussion)
  • Re: Change Text to Memo
    ... Sorry I didn't initially mention that the database is elsewhere. ... Switch a given table field to Memo ... Function SwitchFieldType(sDb As String, sTableName As String, sFieldName ... Dim sSQL As String ...
    (microsoft.public.access.modulesdaovba)
Quantcast