upgrading to vb.net

4 Dec 2006 8:51 AM

verity_susan

Gooday Guys

The firm I work for want to finally make shift to vb.net. We use 6.0
for mainly a load of desktop db apps (accounting - boring I know).
Some of the people that I work with want to try out differrent
languages, but I have always been happy using vb. Will there be much of
a learning curve to cross over?

Thanks
Sue Verity

4 Dec 2006 9:05 AM

Master Programmer

Hello Susan

In my opinion the cold hard answer is YES. The changes from VB 6.0 -
VB.NET are so large that is should really be considered a different
language. Every single concept has changed in every way. It shouldn't
even be called Visual Basic anymore - because it's not either of these
things.

There are some rumours going around that in the next version of Visual
Studio that VB could be removed as one of it's languages. I believe
this to be true, so do many others. It's a shame really because VB
(6.0) used to be such a great language as you know - easy to use - fast
results.

If you are worried about learning something that may be discontinued -
or like me are discusted that MS have changed the language to much,
then you could consider a different language, as your colleages
suggest. I plan to move to PHP (as far from MS as I can get actually).

Hope this helps
Take care
Steve Ray Irwin

verity_su***@yahoo.com.au wrote:

Show quoteHide quote

> Gooday Guys
>
> The firm I work for want to finally make shift to vb.net. We use 6.0
> for mainly a load of desktop db apps (accounting - boring I know).
> Some of the people that I work with want to try out differrent
> languages, but I have always been happy using vb. Will there be much of
> a learning curve to cross over?
>
> Thanks
> Sue Verity

4 Dec 2006 10:49 AM

Branco Medeiros

Master Programmer wrote:

> Hello Susan

It would be more help if you stated "Hello, Master Programmer".

B.

4 Dec 2006 12:49 PM

guy

The two things that will potentially take some time are:-
1-moving to an OO way of thinking
2-discovering the enormous number of classes in the Framework

The changes to VB itself will not be to difficult to master - just things
like an integer is now 32 bit etc.

but once you have you will not want to go back!

hth

Guy

Show quoteHide quote

"verity_su***@yahoo.com.au" wrote:

> Gooday Guys
>
> The firm I work for want to finally make shift to vb.net. We use 6.0
> for mainly a load of desktop db apps (accounting - boring I know).
> Some of the people that I work with want to try out differrent
> languages, but I have always been happy using vb. Will there be much of
> a learning curve to cross over?
>
> Thanks
> Sue Verity
>
>

4 Dec 2006 1:08 PM

BK

The programmers in your organization won't have a problem making the
transition, the people that rely on wizards will. Yes, there is a
learning curve, but I had my first app running in less than a month
with no training. Granted it was a relatively small app, but it
connected to a SQL server for it's data, used some complex grids, and
had a few reports as well.

As for the "rumor" that MS is doing away with VB.Net, that is coming
from one or 2 nut cases that for whatever childish reasons think that
people actually listen to their ramblings. Don't be fooled by the
flamers that lurk in this newsgroup, you can pretty much count on them
to blast everything. Hope this helps, feel free to ask more specific
questions as needed.

BK

4 Dec 2006 2:58 PM

rowe_newsgroups

> The programmers in your organization won't have a problem making the
> transition, the people that rely on wizards will.

BK is right - I also didn't find the switch to VB.Net from VB6 to be
very difficult. But I didn't use wizards in VB6 and I don't use them in
..Net. I would recommend you and your coworkers skim through the first
hundred pages or so of Francesco Balena's "Programming Microsoft Visual
Basic .Net". The book is written for VB6 developers and the first
section(s) are about the major code/syntax/method changes in the .Net
framework.

Thanks,

Seth Rowe

BK wrote:
Show quoteHide quote

> The programmers in your organization won't have a problem making the
> transition, the people that rely on wizards will. Yes, there is a
> learning curve, but I had my first app running in less than a month
> with no training. Granted it was a relatively small app, but it
> connected to a SQL server for it's data, used some complex grids, and
> had a few reports as well.
>
> As for the "rumor" that MS is doing away with VB.Net, that is coming
> from one or 2 nut cases that for whatever childish reasons think that
> people actually listen to their ramblings. Don't be fooled by the
> flamers that lurk in this newsgroup, you can pretty much count on them
> to blast everything. Hope this helps, feel free to ask more specific
> questions as needed.
>
> BK

4 Dec 2006 5:57 PM

RobinS

I think that's the old version of Mr. Balena's book. The new
version is "Programming Microsoft Visual Basic 2005: The Language".
Same idea, though.

Tim Patrick's book is a good introduction as well; it covers all
the major topics and provides lots of code to try out and muck
around with. "Start-to-Finish VB2005".

Robin S.
------------------------------
Show quoteHide quote

"rowe_newsgroups" <rowe_em***@yahoo.com> wrote in message
news:1165244330.330869.308460@j44g2000cwa.googlegroups.com...
>> The programmers in your organization won't have a problem making the
>> transition, the people that rely on wizards will.
>
> BK is right - I also didn't find the switch to VB.Net from VB6 to be
> very difficult. But I didn't use wizards in VB6 and I don't use them in
> .Net. I would recommend you and your coworkers skim through the first
> hundred pages or so of Francesco Balena's "Programming Microsoft Visual
> Basic .Net". The book is written for VB6 developers and the first
> section(s) are about the major code/syntax/method changes in the .Net
> framework.
>
> Thanks,
>
> Seth Rowe
>
>
> BK wrote:
>> The programmers in your organization won't have a problem making the
>> transition, the people that rely on wizards will. Yes, there is a
>> learning curve, but I had my first app running in less than a month
>> with no training. Granted it was a relatively small app, but it
>> connected to a SQL server for it's data, used some complex grids, and
>> had a few reports as well.
>>
>> As for the "rumor" that MS is doing away with VB.Net, that is coming
>> from one or 2 nut cases that for whatever childish reasons think that
>> people actually listen to their ramblings. Don't be fooled by the
>> flamers that lurk in this newsgroup, you can pretty much count on them
>> to blast everything. Hope this helps, feel free to ask more specific
>> questions as needed.
>>
>> BK
>

6 Dec 2006 6:00 AM

verity_susan

Wow, thanks for all of the advice, its really helpful. You guys all
seem very emotive about this ! My panties are wet with laughter.

Susan

verity_su***@yahoo.com.au wrote:
Show quoteHide quote

> Gooday Guys
>
> The firm I work for want to finally make shift to vb.net. We use 6.0
> for mainly a load of desktop db apps (accounting - boring I know).
> Some of the people that I work with want to try out differrent
> languages, but I have always been happy using vb. Will there be much of
> a learning curve to cross over?
>
> Thanks
> Sue Verity