upgrading to vb.net

[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

[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

[e-mail] 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

[Branco Medeiros]

Master Programmer wrote:

Hello Susan

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

B.

[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

"ve**********@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

[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

[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:

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

[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.
------------------------------
"rowe_newsgroups" <ro********@yahoo.comwrote in message
news:11**********************@j44g2000cwa.googlegr oups.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

[aaron.kempf]

VB.net _IS_ going away

http://www.eweek.com/article2/0,1895,2065392,00.asp

According to Evans Data's Fall 2006 North American Development Survey,
overall, developer use of the Visual Basic family has dropped off by 35
percent since last spring.

Moreover, Evans said, "As expected, developers are finally leaving VB6
and earlier versions; they're also leaving VB.NET; which is down by 26
percent. This means Java now holds the market penetration lead at 45
percent, followed by C/C++ at 40 percent, and C# at 32 percent."



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

[BK]

What I find most amusing about you, even more than your mind numbing
number of aliases, is that you spend so much time in a newsgroup
devoted to a product you despise. You are entertaining if nothing else.

[aaron.kempf]

MS Killed the most popular langauge; and I've seen too many people go
into VB.net.. when all of the jobs are in C#

seattle.craigslist.org has a difference of 5:1 of C# vs VB.net jobs

I'll personally never ever ever use C#

but for most people out there; it would make more sense

-Aaron
BK wrote:

What I find most amusing about you, even more than your mind numbing
number of aliases, is that you spend so much time in a newsgroup
devoted to a product you despise. You are entertaining if nothing else.

[rowe_newsgroups]

MS Killed the most popular langauge; and I've seen too many people go

into VB.net.. when all of the jobs are in C#

Ah finally a well stated and helpful post from Aaron! I'll still
disagree that MS killed Visual Basic, but that argument has been beat
to death. But when it comes down to it, Microsoft is a business, and
businesses (good one's at least) produce the products that are in
demand. If there are more Java/C/C++ developers wanting something from
Microsoft then they will win out on who gets the most attention (C# or
VB). After we can probably all agree Microsoft loves money, so why
wouldn't they please the highest bidder? The danger is that the more
people you and others turn away from Visual Basic than the less
Microsoft is going to care about the status of vb. I would suggest you
focus your efforts on getting people to write Microsoft and voice their
opinions. (Remember there are more people than just you that want MS to
put more effort into developing/supporting Visual Basic)

seattle.craigslist.org has a difference of 5:1 of C# vs VB.net jobs

Remember, this just means there are more available jobs in C# than in
Visual Basic. This could be because (like you mentioned in another
thread) that college's are turning out more VB graduates than C#
graduates. If this is true than the VB.Net jobs are probally being
filled quickly while the C# jobs just sit there waited for applicants.
I would be interested to see what the salary differences are between
the C# and VB jobs, which could be a better indicator of which jobs are
in higher demand.

Finally, IDE aside, can we agree that the language changes (or at least
most parts of the language changes) were good for Visual Basic? I
definately agree with you that the IDE has some severe problems that
Microsoft needs to address - one of which is the VB compiler which I
too have problems with daily (and no the hotfix didn't work) But again
the more well-writen complaints (abusive complaints will just end up in
the trash) that Microsoft receives the greater the odds of them fixing
the ide are.

Thanks,

Seth Rowe
aa*********@gmail.com wrote:

MS Killed the most popular langauge; and I've seen too many people go
into VB.net.. when all of the jobs are in C#

seattle.craigslist.org has a difference of 5:1 of C# vs VB.net jobs

I'll personally never ever ever use C#

but for most people out there; it would make more sense

-Aaron
BK wrote:

What I find most amusing about you, even more than your mind numbing
number of aliases, is that you spend so much time in a newsgroup
devoted to a product you despise. You are entertaining if nothing else.

[aaron.kempf]

they didn't 'please the highest bidder' and they didn't 'please the
most populous bidder'

they pleased the C++ and java fags that were irrelevent anyways

-Aaron
rowe_newsgroups wrote:

MS Killed the most popular langauge; and I've seen too many people go
into VB.net.. when all of the jobs are in C#

Ah finally a well stated and helpful post from Aaron! I'll still
disagree that MS killed Visual Basic, but that argument has been beat
to death. But when it comes down to it, Microsoft is a business, and
businesses (good one's at least) produce the products that are in
demand. If there are more Java/C/C++ developers wanting something from
Microsoft then they will win out on who gets the most attention (C# or
VB). After we can probably all agree Microsoft loves money, so why
wouldn't they please the highest bidder? The danger is that the more
people you and others turn away from Visual Basic than the less
Microsoft is going to care about the status of vb. I would suggest you
focus your efforts on getting people to write Microsoft and voice their
opinions. (Remember there are more people than just you that want MS to
put more effort into developing/supporting Visual Basic)

seattle.craigslist.org has a difference of 5:1 of C# vs VB.net jobs

Remember, this just means there are more available jobs in C# than in
Visual Basic. This could be because (like you mentioned in another
thread) that college's are turning out more VB graduates than C#
graduates. If this is true than the VB.Net jobs are probally being
filled quickly while the C# jobs just sit there waited for applicants.
I would be interested to see what the salary differences are between
the C# and VB jobs, which could be a better indicator of which jobs are
in higher demand.

Finally, IDE aside, can we agree that the language changes (or at least
most parts of the language changes) were good for Visual Basic? I
definately agree with you that the IDE has some severe problems that
Microsoft needs to address - one of which is the VB compiler which I
too have problems with daily (and no the hotfix didn't work) But again
the more well-writen complaints (abusive complaints will just end up in
the trash) that Microsoft receives the greater the odds of them fixing
the ide are.

Thanks,

Seth Rowe
aa*********@gmail.com wrote:

MS Killed the most popular langauge; and I've seen too many people go
into VB.net.. when all of the jobs are in C#

seattle.craigslist.org has a difference of 5:1 of C# vs VB.net jobs

I'll personally never ever ever use C#

but for most people out there; it would make more sense

-Aaron
BK wrote:

What I find most amusing about you, even more than your mind numbing
number of aliases, is that you spend so much time in a newsgroup
devoted to a product you despise. You are entertaining if nothing else.

[aaron.kempf]

I hope to scare people away from VB because I 'heard that they are
going to kill it'
rowe_newsgroups wrote:

MS Killed the most popular langauge; and I've seen too many people go
into VB.net.. when all of the jobs are in C#

Ah finally a well stated and helpful post from Aaron! I'll still
disagree that MS killed Visual Basic, but that argument has been beat
to death. But when it comes down to it, Microsoft is a business, and
businesses (good one's at least) produce the products that are in
demand. If there are more Java/C/C++ developers wanting something from
Microsoft then they will win out on who gets the most attention (C# or
VB). After we can probably all agree Microsoft loves money, so why
wouldn't they please the highest bidder? The danger is that the more
people you and others turn away from Visual Basic than the less
Microsoft is going to care about the status of vb. I would suggest you
focus your efforts on getting people to write Microsoft and voice their
opinions. (Remember there are more people than just you that want MS to
put more effort into developing/supporting Visual Basic)

seattle.craigslist.org has a difference of 5:1 of C# vs VB.net jobs

Remember, this just means there are more available jobs in C# than in
Visual Basic. This could be because (like you mentioned in another
thread) that college's are turning out more VB graduates than C#
graduates. If this is true than the VB.Net jobs are probally being
filled quickly while the C# jobs just sit there waited for applicants.
I would be interested to see what the salary differences are between
the C# and VB jobs, which could be a better indicator of which jobs are
in higher demand.

Finally, IDE aside, can we agree that the language changes (or at least
most parts of the language changes) were good for Visual Basic? I
definately agree with you that the IDE has some severe problems that
Microsoft needs to address - one of which is the VB compiler which I
too have problems with daily (and no the hotfix didn't work) But again
the more well-writen complaints (abusive complaints will just end up in
the trash) that Microsoft receives the greater the odds of them fixing
the ide are.

Thanks,

Seth Rowe
aa*********@gmail.com wrote:

MS Killed the most popular langauge; and I've seen too many people go
into VB.net.. when all of the jobs are in C#

seattle.craigslist.org has a difference of 5:1 of C# vs VB.net jobs

I'll personally never ever ever use C#

but for most people out there; it would make more sense

-Aaron
BK wrote:

What I find most amusing about you, even more than your mind numbing
number of aliases, is that you spend so much time in a newsgroup
devoted to a product you despise. You are entertaining if nothing else.

[aaron.kempf]

and I was a peachy pro-microsoft kid for 10 years and Microsoft never
did anything but DID ME WRONG

fired me for speaking the truth.
they wouldn't return my own personal laptop after firing me.

I dont believe that MS listens to well written complaints.
where is the PUBLIC WEBSITE THE TRACKS THESE PUBLIC COMPLAINTS AND
OPENS THE WHOLE DISCUSSION TO THE PUBLIC?

I'm DISENFRANCHISED from the whole MIcrosoft military-industrial
complex.
they are fucking evil.

Fuck that company; the only thing that I need to convey do you kids is
'fuck microsoft, leave ms and go learn PHP'

PHP is vastly more popular than any langauge MS has ever written..
according to netcraft.com

MS screwed the pooch and I'll be damned if I ever vote for them with MY
SKILLSET again.

Long live dreamweaver, PHP and mySql

-Aaron


rowe_newsgroups wrote:

MS Killed the most popular langauge; and I've seen too many people go
into VB.net.. when all of the jobs are in C#

Ah finally a well stated and helpful post from Aaron! I'll still
disagree that MS killed Visual Basic, but that argument has been beat
to death. But when it comes down to it, Microsoft is a business, and
businesses (good one's at least) produce the products that are in
demand. If there are more Java/C/C++ developers wanting something from
Microsoft then they will win out on who gets the most attention (C# or
VB). After we can probably all agree Microsoft loves money, so why
wouldn't they please the highest bidder? The danger is that the more
people you and others turn away from Visual Basic than the less
Microsoft is going to care about the status of vb. I would suggest you
focus your efforts on getting people to write Microsoft and voice their
opinions. (Remember there are more people than just you that want MS to
put more effort into developing/supporting Visual Basic)

seattle.craigslist.org has a difference of 5:1 of C# vs VB.net jobs

Remember, this just means there are more available jobs in C# than in
Visual Basic. This could be because (like you mentioned in another
thread) that college's are turning out more VB graduates than C#
graduates. If this is true than the VB.Net jobs are probally being
filled quickly while the C# jobs just sit there waited for applicants.
I would be interested to see what the salary differences are between
the C# and VB jobs, which could be a better indicator of which jobs are
in higher demand.

Finally, IDE aside, can we agree that the language changes (or at least
most parts of the language changes) were good for Visual Basic? I
definately agree with you that the IDE has some severe problems that
Microsoft needs to address - one of which is the VB compiler which I
too have problems with daily (and no the hotfix didn't work) But again
the more well-writen complaints (abusive complaints will just end up in
the trash) that Microsoft receives the greater the odds of them fixing
the ide are.

Thanks,

Seth Rowe
aa*********@gmail.com wrote:

MS Killed the most popular langauge; and I've seen too many people go
into VB.net.. when all of the jobs are in C#

seattle.craigslist.org has a difference of 5:1 of C# vs VB.net jobs

I'll personally never ever ever use C#

but for most people out there; it would make more sense

-Aaron
BK wrote:

What I find most amusing about you, even more than your mind numbing
number of aliases, is that you spend so much time in a newsgroup
devoted to a product you despise. You are entertaining if nothing else.

[rowe_newsgroups]

they didn't 'please the highest bidder' and they didn't 'please the

most populous bidder'

they pleased the C++ and java fags that were irrelevent anyways

This is what I meant in my post - as I understand C# was made to
attract C, C++, and Java developers. So if there are more C++ and Java
developers to please than visual basic developers than MS would put the
more effort into C#

Thanks,

Seth Rowe
aa*********@gmail.com wrote:

they didn't 'please the highest bidder' and they didn't 'please the
most populous bidder'

they pleased the C++ and java fags that were irrelevent anyways

-Aaron
rowe_newsgroups wrote:

MS Killed the most popular langauge; and I've seen too many people go
into VB.net.. when all of the jobs are in C#

Ah finally a well stated and helpful post from Aaron! I'll still
disagree that MS killed Visual Basic, but that argument has been beat
to death. But when it comes down to it, Microsoft is a business, and
businesses (good one's at least) produce the products that are in
demand. If there are more Java/C/C++ developers wanting something from
Microsoft then they will win out on who gets the most attention (C# or
VB). After we can probably all agree Microsoft loves money, so why
wouldn't they please the highest bidder? The danger is that the more
people you and others turn away from Visual Basic than the less
Microsoft is going to care about the status of vb. I would suggest you
focus your efforts on getting people to write Microsoft and voice their
opinions. (Remember there are more people than just you that want MS to
put more effort into developing/supporting Visual Basic)

seattle.craigslist.org has a difference of 5:1 of C# vs VB.net jobs

Remember, this just means there are more available jobs in C# than in
Visual Basic. This could be because (like you mentioned in another
thread) that college's are turning out more VB graduates than C#
graduates. If this is true than the VB.Net jobs are probally being
filled quickly while the C# jobs just sit there waited for applicants.
I would be interested to see what the salary differences are between
the C# and VB jobs, which could be a better indicator of which jobs are
in higher demand.

Finally, IDE aside, can we agree that the language changes (or at least
most parts of the language changes) were good for Visual Basic? I
definately agree with you that the IDE has some severe problems that
Microsoft needs to address - one of which is the VB compiler which I
too have problems with daily (and no the hotfix didn't work) But again
the more well-writen complaints (abusive complaints will just end up in
the trash) that Microsoft receives the greater the odds of them fixing
the ide are.

Thanks,

Seth Rowe
aa*********@gmail.com wrote:

MS Killed the most popular langauge; and I've seen too many people go
into VB.net.. when all of the jobs are in C#
>
seattle.craigslist.org has a difference of 5:1 of C# vs VB.net jobs
>
I'll personally never ever ever use C#
>
but for most people out there; it would make more sense
>
-Aaron
>
>
BK wrote:
What I find most amusing about you, even more than your mind numbing
number of aliases, is that you spend so much time in a newsgroup
devoted to a product you despise. You are entertaining if nothing else.

[rowe_newsgroups]

Well, I see your posts have degraded into swearing and flaming again
*sigh*

You do realize that you would be much more effective in your "campaign"
against Microsoft if you stopped all the swearing and flame posts
right? By continuing to be abusive, people will get the impression that
you don't know what you're talking about - and are probably just
flaming because you're sitting at home with nothing better to do.

Again, if you want to gain credibility clean up your posts and engage
us in a civilized manner.

Thanks,

Seth Rowe
aa*********@gmail.com wrote:

and I was a peachy pro-microsoft kid for 10 years and Microsoft never
did anything but DID ME WRONG

fired me for speaking the truth.
they wouldn't return my own personal laptop after firing me.

I dont believe that MS listens to well written complaints.
where is the PUBLIC WEBSITE THE TRACKS THESE PUBLIC COMPLAINTS AND
OPENS THE WHOLE DISCUSSION TO THE PUBLIC?

I'm DISENFRANCHISED from the whole MIcrosoft military-industrial
complex.
they are fucking evil.

Fuck that company; the only thing that I need to convey do you kids is
'fuck microsoft, leave ms and go learn PHP'

PHP is vastly more popular than any langauge MS has ever written..
according to netcraft.com

MS screwed the pooch and I'll be damned if I ever vote for them with MY
SKILLSET again.

Long live dreamweaver, PHP and mySql

-Aaron


rowe_newsgroups wrote:

MS Killed the most popular langauge; and I've seen too many people go
into VB.net.. when all of the jobs are in C#

Ah finally a well stated and helpful post from Aaron! I'll still
disagree that MS killed Visual Basic, but that argument has been beat
to death. But when it comes down to it, Microsoft is a business, and
businesses (good one's at least) produce the products that are in
demand. If there are more Java/C/C++ developers wanting something from
Microsoft then they will win out on who gets the most attention (C# or
VB). After we can probably all agree Microsoft loves money, so why
wouldn't they please the highest bidder? The danger is that the more
people you and others turn away from Visual Basic than the less
Microsoft is going to care about the status of vb. I would suggest you
focus your efforts on getting people to write Microsoft and voice their
opinions. (Remember there are more people than just you that want MS to
put more effort into developing/supporting Visual Basic)

seattle.craigslist.org has a difference of 5:1 of C# vs VB.net jobs

Remember, this just means there are more available jobs in C# than in
Visual Basic. This could be because (like you mentioned in another
thread) that college's are turning out more VB graduates than C#
graduates. If this is true than the VB.Net jobs are probally being
filled quickly while the C# jobs just sit there waited for applicants.
I would be interested to see what the salary differences are between
the C# and VB jobs, which could be a better indicator of which jobs are
in higher demand.

Finally, IDE aside, can we agree that the language changes (or at least
most parts of the language changes) were good for Visual Basic? I
definately agree with you that the IDE has some severe problems that
Microsoft needs to address - one of which is the VB compiler which I
too have problems with daily (and no the hotfix didn't work) But again
the more well-writen complaints (abusive complaints will just end up in
the trash) that Microsoft receives the greater the odds of them fixing
the ide are.

Thanks,

Seth Rowe
aa*********@gmail.com wrote:

MS Killed the most popular langauge; and I've seen too many people go
into VB.net.. when all of the jobs are in C#
>
seattle.craigslist.org has a difference of 5:1 of C# vs VB.net jobs
>
I'll personally never ever ever use C#
>
but for most people out there; it would make more sense
>
-Aaron
>
>
BK wrote:
What I find most amusing about you, even more than your mind numbing
number of aliases, is that you spend so much time in a newsgroup
devoted to a product you despise. You are entertaining if nothing else.

[Stephany Young]

Careful BK.

You managed to post this as a response to your earlier post so it appears as
if you are berating yourself.

If you are actually aiming this at the so-called 'Master Programmer' and his
other aliases then I think the appropriate word is 'pathetic' rather than
'entertaining'.
"BK" <bk******@hotmail.comwrote in message
news:11**********************@73g2000cwn.googlegro ups.com...

What I find most amusing about you, even more than your mind numbing
number of aliases, is that you spend so much time in a newsgroup
devoted to a product you despise. You are entertaining if nothing else.

[aaron.kempf]

you're full of fucking shit dude

everyone in the world agrees that VB _WAS_ the worlds most popular
language.
Oreilly.. Microsoft.. I've read this in literally a dozen impartial
places... VB is and always has been more popular than any other
language.. until these past 3 or 4 years; ever since Microsoft put VB
on a skewer and killed it with verbosity and complexity.

Microsoft MIS-DIAGNOSED THE MARKET and put the effort into attracting
Java and C++ _FAGS_ when they should have paid attention to VB6 / VBA
/ VBS developers.

WE OUT NUMBERED THEM AND MICROSOFT WAS RUN BY A BUNCH OF EXCEL DORKS
AND C++ FAGS SO THEY MADE THE WRONG MOVE.

We're not 'junior programmers' we were 'enlightened programmers' and
I'll be damned-- I'll never use Java CRAP or C++ crap. And I would
rather work at McDonalds than use C#

And I'm just glad that this debacle is almost over; they'll announce it
soon.. that VB 10 will never be.. and VB 9 will hopefully get
cancelled.

The C++ fags won.
and Microsoft admitted defeat when they first saw a baby little
retarded company named Sun hawking this shit ass language named JAVA.

Rather then put up a good fight-- Microsoft has folded their winning
hand and surrendered VB.

I just urge you guys-- don't let MS do this twice.
Move to Dreamweaver / PHP / mySql... Microsoft can't accidently kill
that language LoL

-Aaron Kempf
PHP developer
rowe_newsgroups wrote:

they didn't 'please the highest bidder' and they didn't 'please the
most populous bidder'

they pleased the C++ and java fags that were irrelevent anyways

This is what I meant in my post - as I understand C# was made to
attract C, C++, and Java developers. So if there are more C++ and Java
developers to please than visual basic developers than MS would put the
more effort into C#

Thanks,

Seth Rowe
aa*********@gmail.com wrote:

they didn't 'please the highest bidder' and they didn't 'please the
most populous bidder'

they pleased the C++ and java fags that were irrelevent anyways

-Aaron
rowe_newsgroups wrote:

MS Killed the most popular langauge; and I've seen too many people go
into VB.net.. when all of the jobs are in C#
>
Ah finally a well stated and helpful post from Aaron! I'll still
disagree that MS killed Visual Basic, but that argument has been beat
to death. But when it comes down to it, Microsoft is a business, and
businesses (good one's at least) produce the products that are in
demand. If there are more Java/C/C++ developers wanting something from
Microsoft then they will win out on who gets the most attention (C# or
VB). After we can probably all agree Microsoft loves money, so why
wouldn't they please the highest bidder? The danger is that the more
people you and others turn away from Visual Basic than the less
Microsoft is going to care about the status of vb. I would suggest you
focus your efforts on getting people to write Microsoft and voice their
opinions. (Remember there are more people than just you that want MS to
put more effort into developing/supporting Visual Basic)
>
seattle.craigslist.org has a difference of 5:1 of C# vs VB.net jobs
>
Remember, this just means there are more available jobs in C# than in
Visual Basic. This could be because (like you mentioned in another
thread) that college's are turning out more VB graduates than C#
graduates. If this is true than the VB.Net jobs are probally being
filled quickly while the C# jobs just sit there waited for applicants.
I would be interested to see what the salary differences are between
the C# and VB jobs, which could be a better indicator of which jobs are
in higher demand.
>
Finally, IDE aside, can we agree that the language changes (or at least
most parts of the language changes) were good for Visual Basic? I
definately agree with you that the IDE has some severe problems that
Microsoft needs to address - one of which is the VB compiler which I
too have problems with daily (and no the hotfix didn't work) But again
the more well-writen complaints (abusive complaints will just end up in
the trash) that Microsoft receives the greater the odds of them fixing
the ide are.
>
Thanks,
>
Seth Rowe
>
>
aa*********@gmail.com wrote:
MS Killed the most popular langauge; and I've seen too many people go
into VB.net.. when all of the jobs are in C#

seattle.craigslist.org has a difference of 5:1 of C# vs VB.net jobs

I'll personally never ever ever use C#

but for most people out there; it would make more sense

-Aaron


BK wrote:
What I find most amusing about you, even more than your mind numbing
number of aliases, is that you spend so much time in a newsgroup
devoted to a product you despise. You are entertaining if nothing else.

[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
ve**********@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