Jim Burns said:
What really made up my mind was watching The.net Show. I watched VB.net
And
loved the idea that they said they made VB a first class language with
.net
Not a lot of API calls to get to the hart of the OS .At the time I didn't
know about all this controversy after all the same people that wrote
VB1,2,3,4,5,6,Wrote VB.net
Sorry... nice thought but, same company. Completely different development
team....All of those API calls, and other non "plain vanilla basic" code
that we've been adding to our apps for years and years, are completely
debugged and very reliable, have to be thrown away in this "language of the
month" they're calling VB.Net (aka B#). The upgrade "wizard" is worthless on
anything but "plain vanilla basic" and even then, it falls way short of
being a useful tool. The complete loss of a decade's worth of handy code
snips and components is what's keeping "the masses" from adopting B#. There
are a lot of companies doing all of their new work in .Net. Not too many
that are paying people to re-write, test, debug and redeploy tons of code
just so they can say "but, it's .Net!". We have components here that have
been in use for 5+ years without costing the company another dime becuase
they're fully debugged and suit the purpose they were designed for very
well. Why would anyone want to toss that reliability in the trash and start
over.net?
I couldn't find any video tapes for learning .net as a true beginner. So I
purchase 17 VB6 CDs and 18 VB.net CDs
Tons and tons of videos on both. If you have problems finding tutorials on
VB.anything, post back. There are a bajillion of each.
I'm more then half way thru VB6 And I've tried what I learned in VB.net
I'm
Half way through the videos maybe.. I've been writing VB code for as as long
as I can remember and I'm still not "half way through" using all of the
capabilities of the language.
a beginner and it wasn't like a different language it seemed like VB.
I did notice they went a little to far with Changing stupid stuff like
combo1.AddItem and many more. No Control Arrays with out having to write
your own Array handler. But Like it or not it is VB7 and if for one moment
I
thought otherwise I would learn C++ and I think New programmers would
agree.
You may want to reconsider. C++ devs make the most money for one thing and
they can actually use code that's years old without worrying about some
software company changing it on a whim.
Because if VB.net wasn't VB who would want to learn a dieing language. A
people who believe the marketting hype. Here are a few opinions that aren't
tied to sales.
Visual Fred
http://www.mvps.org/vb/index2.html?rants/vfred.htm
Our statement on VB.Net
http://www.microdexterity.com/staminet.html
....If I looked hard enough, I could find many more where those came from.
language that would never be upgraded again. From what little I know I
would
love for Microsoft to Change .net . Not back to vb6 but put back the
syntax
arrays and more . but It will never happen. So Ill learn VB6 and then move
on to VB.net
Good luck to you <g> Since you state that you're a beginner, you have quite
a few options. Delphi is another option and quite a few "ex-vb'er's" are
switching to that.
btw, you might want to look around the web. When you find components that
are "100% .Net authored" (or something similar), you can be sure that you'll
find "C#" tied to that statement somewhere on the page. I've never found a
single company that states that their components are written using
"VB.Net"..... not even one company!
I realize many programmers Have used VB for years and feel a strong
attachment with It and Hate what MS did with it.But It is the future of
VB.
Only time will tell. Meanwhile, I have work to do... programming in VB
Classic.
Eventually I feel Microsoft will make the .net framework the only frame
work
for windows Not in the near further but at so point.
That's for sure.... and when that OS becomes popular, it will truly be the
end of Visual Basic. I feel that .Net's still in its infancy and resembles
Win3.1 running on top of DOS (I had that loaded for about a week)...
currently you have the .Net framework running on top of Windows. When they
get rid of the "running on top of" part of the description, things will
speed up and run more smoothly and it'll be about as different (hopefully,
improved) as Win95/NT4 was when compared to Win3.1/NT3.51(ick). I'm patient.
I'll wait. As Grandma used to say, "anything worth having is worth waiting
for" (that statement doesn't apply to waiting for a programming language to
populate a form though <g>)