Re: Moving from VB6 to dot net
From: raaco (<)
Date: 09/27/04
- Next message: Jay B. Harlow [MVP - Outlook]: "Re: how to make array of arrays?"
- Previous message: Jay B. Harlow [MVP - Outlook]: "Re: Property Modified (dirty)"
- In reply to: aaj: "Moving from VB6 to dot net"
- Next in thread: Xander: "Re: Moving from VB6 to dot net"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 27 Sep 2004 17:04:46 +0100
To add to the other two replies, you also need to know that
visual studio requires 512mb ram (i.e. if your computer is
256mb, then you will be struggling).
Also, all your apps will need the .net run-time
(known as the dotnet framework) and this is 22mb
Personally, I treat dotnet as another tool rather than
a replacement tool, because for some things vb6 will still be
the way to go, even today, because of the minimalist nature
of vb6 compared to dotnet. But I do recommend learning
dotnet, even if you are not going to use it. This will teach
you how to do things the right way, you won't regret it.
Dotnet is a state of the art tool, any real programmer will
surely not want to skip learning it.
"aaj" <a.b@c.com> wrote in message
news:415814e5$0$13717$afc38c87@news.easynet.co.uk...
> 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
>
>
>
- Next message: Jay B. Harlow [MVP - Outlook]: "Re: how to make array of arrays?"
- Previous message: Jay B. Harlow [MVP - Outlook]: "Re: Property Modified (dirty)"
- In reply to: aaj: "Moving from VB6 to dot net"
- Next in thread: Xander: "Re: Moving from VB6 to dot net"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
