Moving from VB6 to dot net

[aaj]

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

[solex]

Andy,

If all you are writing is simple desktop apps that integrate with a database
you might reconsider using Access. I believe it is the most efficient for
creating simple data access apps. I program in Dot Net and VB6 and can say
that for complicated stuff with OO there is no comparision .NET wins, .NET
is also much better for creating web apps. But as far as simple desktop
apps VB6 is still good and some case faster then .NET

Dan
"aaj" <a.*@c.com> wrote in message
news:41***********************@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

[Cor Ligthert]

Hi Aaj,

I have seen a lot of messages in this newsgroup that where in the kind of,
"when I have to go back to VB6 they have to push me and I will scream loud".

Cor

[raaco]

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.*@c.com> wrote in message
news:41***********************@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

[Xander]

> 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?

Believe me: It is so much more fun developing .NET. Only because of that
your TTM will already increase rapidly. :)
--
http://www.dotnet4all.com
The first open content-editable .NET knowledgebase.
Just double-click to contribute your knowledge.

[aaj]

Hi all

Thanks for the advice so far

From a personal point of view I want to switch to dot net and develop my
skills, but that said I have to be aware of the effects that the change will
have on the other guys in the company who work with me... if I go, they will
have to change as well, so I can't make the decision without taking a
detached view.

I have read that with VB dot net, the language is much more akin to c++ and
you get extra functionality at lower levels over VB6, is this the case and
what other advantages does VB dot net have.

How difficult is it to switch to an object orientated language, the problem
for me is that my OO skills are some where between lacking and non existent,
unfortunately my background has been PLC ladder/instruction lists, then C
(not c++) and then VB6, but the stuff I write tends to be more function
based sequences, rather than full blow OO.

Thanks for your time in helping me out here, its refreshing to be able to
ask questions of people who use this stuff rather than just reading the
marketing material

thanks again

Andy

"aaj" <a.*@c.com> wrote in message
news:41***********************@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

[raaco]

"aaj" <a.*@c.com> wrote in message
news:41***********************@news.easynet.co.uk. ..

Hi all

Thanks for the advice so far

From a personal point of view I want to switch to dot net and develop my
skills, but that said I have to be aware of the effects that the change will have on the other guys in the company who work with me... if I go, they will have to change as well, so I can't make the decision without taking a
detached view.

I have read that with VB dot net, the language is much more akin to c++ and you get extra functionality at lower levels over VB6, is this the case and
what other advantages does VB dot net have.
Yes, VB7 (dotnet) has "borrowed" a lot of syntax from C++ , but you will be
happy to hear, not pointers, so there should be no problems. As there are
no pointers in VB, there is no "low-level" support, so no, VB7 is not
more low level.

How difficult is it to switch to an object orientated language, the problem for me is that my OO skills are some where between lacking and non existent, unfortunately my background has been PLC ladder/instruction lists, then C
(not c++) and then VB6, but the stuff I write tends to be more function
based sequences, rather than full blow OO.
It is easy, because you can still work in a non OO way on VB7 simply
by ignoring the new features, so you can gradually learn the techniques.
Also, I find, it is easier to first do something in a non OO way, and then
when it's finished, to try to "re-factorise" it into OO. The reason for this
is
that when you program sequencially (as opposed to OO) you can more
clearly see which variables and functions you need.

Thanks for your time in helping me out here, its refreshing to be able to
ask questions of people who use this stuff rather than just reading the
marketing material

thanks again

Andy

"aaj" <a.*@c.com> wrote in message
news:41***********************@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

[Bob]

Once you have a dawning understanding of good OO design, which will probably
be halfway or most of the way through the translation of your VB6 projects,
you'll realize that there are so many improvements and simplifications you
can make to the design that you'll end up concluding that it all needs to be
rewritten. Not just refactored, since you started out without a good grasp
of OO, but completely rewritten. And this perhaps could be avoided.

Once you're familiar with the language and syntax (after self-learning or
courses) buy "Design Patterns, Elements of Reusable Object Oriented
Software". Read through it, make yourself test projects to play with the
different ways of doing things. I had an old professor back in college that
said that every minute spent in the design phase of a project will have a
factor of twenty impact later... or something to that effect. It's true. If
time matters to you, refrain from jumping into translating your projects
(or, at least, committing to the first attempts) without gaining a good
understanding of OO first.

You could also bring someone in with relevant experience and get direction
and advice that could save you from reinventing the wheel and maybe months
of development. Go to your local DotNet user's group and network it up. If
you go to a Boston meeting (http://www.bostondotnet.org/), I'll be one of
the people offering to help.

Bob

"aaj" <a.*@c.com> wrote in message
news:41***********************@news.easynet.co.uk. ..

Hi all

Thanks for the advice so far

From a personal point of view I want to switch to dot net and develop my
skills, but that said I have to be aware of the effects that the change will have on the other guys in the company who work with me... if I go, they will have to change as well, so I can't make the decision without taking a
detached view.

I have read that with VB dot net, the language is much more akin to c++ and you get extra functionality at lower levels over VB6, is this the case and
what other advantages does VB dot net have.

How difficult is it to switch to an object orientated language, the problem for me is that my OO skills are some where between lacking and non existent, unfortunately my background has been PLC ladder/instruction lists, then C
(not c++) and then VB6, but the stuff I write tends to be more function
based sequences, rather than full blow OO.

Thanks for your time in helping me out here, its refreshing to be able to
ask questions of people who use this stuff rather than just reading the
marketing material

thanks again

Andy