My OPINION (note the word of opinion, as in, everybody has one) would be to
try csharp. This will allow you to leave your (bad) vb6 habits behind you
for the most part.
...
You can stick with vb.net as well.
My vb.net suggestions:
Exception Handling? (ErrorHandling)
Take the vb6 mentality of exception handling and do the 4 following things:
1. Put it in a brown paper bag.
2. Take it to someone's house you don't like.
3. Set it on fire.
4. Run away from it as fast as you can.
If you're using "resume next" in your VB code, then do NOT bring it forward
to .Net. Just
because you ~can~ doesn't mean you ~should~.
Another one:
ADO is NOT ADO.NET. Learn about the IDataReader and the strong DataSet.
Another one:
ASP.NET is NOT ASP.
Another one:
Put
Option Explicit On
Option Strict On
at the top of your classes, until you figure out how you can do it on a
project setting level. This will help you avoid the old vb6 stuff like
dim x
or
dim x as variant
Throw that mindset out the window.
...
This is just one area where your mentality will need to change some.
But try the free book above.
I may be a few blasts from some other posters. That's fine. These are
OPINIONS.
Keep in mind I coded VB4, VB5, and VB6 for over 6 years. It was my bread
and butter for a long time.
And gosh I wish someone had given me some better guidance than I got when I
went from VB6 to VB.Net.
I ended up going to csharp so I could avoid all the vb.net stuff that you're
allowed to do, but you shouldn't do.
Good luck.
"dman" <dman@aol.comwr ote in message
news:OoWG%23qwy IHA.2340@TK2MSF TNGP04.phx.gbl. ..
Hi.
>
Can you recommend any books or courses to learn .net if one
has been using VB6 for many years?
>
Thanks.
>
>
My OPINION (note the word of opinion, as in, everybody has one) would be
to try csharp. This will allow you to leave your (bad) vb6 habits behind
you for the most part.
>
..
>
You can stick with vb.net as well.
>
My vb.net suggestions:
>
Exception Handling? (ErrorHandling)
>
Take the vb6 mentality of exception handling and do the 4 following
things:
>
1. Put it in a brown paper bag.
2. Take it to someone's house you don't like.
3. Set it on fire.
4. Run away from it as fast as you can.
>
..
>
Check here:
>
>
If you're using "resume next" in your VB code, then do NOT bring it
forward to .Net. Just
because you ~can~ doesn't mean you ~should~.
>
>
Another one:
ADO is NOT ADO.NET. Learn about the IDataReader and the strong DataSet.
>
Another one:
ASP.NET is NOT ASP.
>
Another one:
Put
Option Explicit On
Option Strict On
>
at the top of your classes, until you figure out how you can do it on a
project setting level. This will help you avoid the old vb6 stuff like
dim x
or
dim x as variant
>
Throw that mindset out the window.
>
>
..
>
>
This is just one area where your mentality will need to change some.
But try the free book above.
>
>
>
>
>
I may be a few blasts from some other posters. That's fine. These are
OPINIONS.
Keep in mind I coded VB4, VB5, and VB6 for over 6 years. It was my bread
and butter for a long time.
And gosh I wish someone had given me some better guidance than I got when
I went from VB6 to VB.Net.
>
I ended up going to csharp so I could avoid all the vb.net stuff that
you're allowed to do, but you shouldn't do.
>
>
>
Good luck.
>
>
"dman" <dman@aol.comwr ote in message
news:OoWG%23qwy IHA.2340@TK2MSF TNGP04.phx.gbl. ..
>Hi.
>>
>Can you recommend any books or courses to learn .net if one
>has been using VB6 for many years?
>>
>Thanks.
>>
My OPINION (note the word of opinion, as in, everybody has one) would be
to try csharp. This will allow you to leave your (bad) vb6 habits behind
you for the most part.
>
You had some arguments with your wife, or is this opinion based on something
more?
I see too many VB6'ers who retain bad habits going to VB.NET.
They want to use the upgrade wizard instead of actually learning the DotNet
framework.
I know some of it is just not knowing any better. But some of it is just
laziness.
...
If one or both of these (below) options existed, I wouldn't hestitate to
recommend vb.net (aka, equal grounding with c#).
Option JustLikeCSharp ON
OR
Option OldLegacyVB6Cra pStillHangingAr ound OFF
...
But alas those aren't available, thus my opinion.
I mean seriously... "Resume Next" ? What year is it?
I also assuming the user means VB.Net with Framework 2.0 or above. I had a
few issues with VB.Net with Framework 1.1, but most of them have been
addressed.
"Cor Ligthert[MVP]" <notmyfirstname @planet.nlwrote in message
news:C54817D8-311C-462D-A126-B34C9BABAD3B@mi crosoft.com...
Sloan,
>
>My OPINION (note the word of opinion, as in, everybody has one) would be
>to try csharp. This will allow you to leave your (bad) vb6 habits behind
>you for the most part.
>>
You had some arguments with your wife, or is this opinion based on
something more?
>
:-)
>
Cor
>
However, as I use both, I wished there was in C# something as VB.Net
behaviour ON.
By instance to replace that odd legacy method in C# to connect a system
message to an EventHandler.
:-)
Cor
"sloan" <sloan@ipass.ne tschreef in bericht
news:%23bQnBTxy IHA.4876@TK2MSF TNGP04.phx.gbl. ..
>
I see too many VB6'ers who retain bad habits going to VB.NET.
>
They want to use the upgrade wizard instead of actually learning the
DotNet framework.
I know some of it is just not knowing any better. But some of it is just
laziness.
>
..
>
If one or both of these (below) options existed, I wouldn't hestitate to
recommend vb.net (aka, equal grounding with c#).
>
Option JustLikeCSharp ON
OR
Option OldLegacyVB6Cra pStillHangingAr ound OFF
>
..
>
But alas those aren't available, thus my opinion.
>
>
I mean seriously... "Resume Next" ? What year is it?
>
>
I also assuming the user means VB.Net with Framework 2.0 or above. I had
a few issues with VB.Net with Framework 1.1, but most of them have been
addressed.
>
>
>
>
"Cor Ligthert[MVP]" <notmyfirstname @planet.nlwrote in message
news:C54817D8-311C-462D-A126-B34C9BABAD3B@mi crosoft.com...
>Sloan,
>>
>>My OPINION (note the word of opinion, as in, everybody has one) would be
>>to try csharp. This will allow you to leave your (bad) vb6 habits
>>behind you for the most part.
>>>
>You had some arguments with your wife, or is this opinion based on
>something more?
>>
>:-)
>>
>Cor
>>
On 2008-06-10, Cor Ligthert[MVP] <notmyfirstname @planet.nlwrote :
Sloan,
>
I think you are right in a kind of way.
>
However, as I use both, I wished there was in C# something as VB.Net
behaviour ON.
>
By instance to replace that odd legacy method in C# to connect a system
message to an EventHandler.
I like the C# way better - so, don't give them any ideas about something like
that nastyness known as WithEvents and Handles... Yuck!
I just found Programming VB.Net (Core Reference) by Balena - from 2002
>
Is that one ok, or is it too outdated?
>
"Kerry Moorman" <KerryMoor...@d iscussions.micr osoft.comwrote in message
>
news:2F59F216-94EB-45F9-9A39-67DC4C0CAC42@mi crosoft.com...
>
>
>
dman,
>
If you already have a strong VB6 background then I would recommend any of
Francesco Balena's books.
>
Kerry Moorman
>
"dman" wrote:
>
Hi.
>
Can you recommend any books or courses to learn .net if one
has been using VB6 for many years?
>
Thanks.- Hide quoted text -
>
- Show quoted text -
I can also suggest to take a look at "Programmin g Visual Basic 2005:
The Language" whose author is Francesco Balena and that book focuses
on .NET 2.0 and VB 2005:
I remember the day I made a new developer add Option Strict On at the
project setting level.
250+ errors.
I was like "good luck dude, you should be outta here by midnight correcting
all your lazy variant coding".
I guess "as integer" or "as Employee" was just too much for the guy to put
in the first time.
"Cor Ligthert[MVP]" <notmyfirstname @planet.nlwrote in message
news:ABB19599-C848-4CFC-B47E-7C284105080B@mi crosoft.com...
Sloan,
>
I think you are right in a kind of way.
>
However, as I use both, I wished there was in C# something as VB.Net
behaviour ON.
>
By instance to replace that odd legacy method in C# to connect a system
message to an EventHandler.
>
:-)
>
Cor
>
"sloan" <sloan@ipass.ne tschreef in bericht
news:%23bQnBTxy IHA.4876@TK2MSF TNGP04.phx.gbl. ..
>>
>I see too many VB6'ers who retain bad habits going to VB.NET.
>>
>They want to use the upgrade wizard instead of actually learning the
>DotNet framework.
>I know some of it is just not knowing any better. But some of it is just
>laziness.
>>
>..
>>
>If one or both of these (below) options existed, I wouldn't hestitate to
>recommend vb.net (aka, equal grounding with c#).
>>
>Option JustLikeCSharp ON
>OR
>Option OldLegacyVB6Cra pStillHangingAr ound OFF
>>
>..
>>
>But alas those aren't available, thus my opinion.
>>
>>
>I mean seriously... "Resume Next" ? What year is it?
>>
>>
>I also assuming the user means VB.Net with Framework 2.0 or above. I had
>a few issues with VB.Net with Framework 1.1, but most of them have been
>addressed.
>>
>>
>>
>>
>"Cor Ligthert[MVP]" <notmyfirstname @planet.nlwrote in message
>news:C54817D 8-311C-462D-A126-B34C9BABAD3B@mi crosoft.com...
>>Sloan,
>>>
>>>My OPINION (note the word of opinion, as in, everybody has one) would
>>>be to try csharp. This will allow you to leave your (bad) vb6 habits
>>>behind you for the most part.
>>>>
>>You had some arguments with your wife, or is this opinion based on
>>something more?
>>>
>>:-)
>>>
>>Cor
>>>
Refractor+ automatically converts between C# and VB.Net, if you need to see
one way or another.
Also, InnerWorkings has self-based learning avaiable, in many subjects.
--
David Glienna
MVP - Visual Developer (Visual Basic)
2006 thru 2008
"kimiraikko nen" <kimiraikkonen8 5@gmail.comwrot e in message
news:e65d7da1-1019-4cfd-a590-b379f2ea3c63@x3 5g2000hsb.googl egroups.com...
On Jun 10, 9:27 pm, "dman" <d...@aol.comwr ote:
I just found Programming VB.Net (Core Reference) by Balena - from 2002
>
Is that one ok, or is it too outdated?
>
"Kerry Moorman" <KerryMoor...@d iscussions.micr osoft.comwrote in message
>
news:2F59F216-94EB-45F9-9A39-67DC4C0CAC42@mi crosoft.com...
>
>
>
dman,
>
If you already have a strong VB6 background then I would recommend any
of
Francesco Balena's books.
>
Kerry Moorman
>
"dman" wrote:
>
Hi.
>
Can you recommend any books or courses to learn .net if one
has been using VB6 for many years?
>
Thanks.- Hide quoted text -
>
- Show quoted text -
I can also suggest to take a look at "Programmin g Visual Basic 2005:
The Language" whose author is Francesco Balena and that book focuses
on .NET 2.0 and VB 2005:
I remember the day I made a new developer add Option Strict On at the
project setting level.
>
250+ errors.
>
How long did it take you to explain that the compiler option didn't
create the errors, that they had been there all the time, and that
turning the option back off wouldn't fix the problems?
Comment