Learning Curve

  • Thread starter Thread starter scorpion53061
  • Start date Start date
S

scorpion53061

Hi,

I am a vb.net guy......(I know boo hiss LOL)

I was thinking of learning C# as well.

Can I expect a hard road of it as far as a learning curve?

As as side note, what made you choose C# over vb.net?
 
The learning curve depends on whether not you are familiar with OOP. If you
are familiar with the C family of languages syntax then the learning curve
is reduced even more. Outside of that, it will take a concerted effort to
get up to speed
 
I think making the transition depends on how heavily you relied on the
VB.NET specific libraries (which helped keep you code compatible with VB6).
If you abandoned them and programmed VB.NET in a purely ".NET way" then I
think you will be fine and the transition will be easy. If not, it will be
a little harder.

R.
 
I've programmed in VB6.0 for like a year and a half and now I have
transfered to C/C++, but C/C++ is very difficult to work under windows(the
gui stuff is hard) so want to have a syntax and OOP programming language
similar to C++ that is easy to make a gui as it is in VB, is C# the answer?
If it is what book would you reccomend me to start learning(I'm interested
in windows applications and Web programming(I 've done a bit of asp)?
 
Scorp: If you understand .NET (which it appears you do), learning Syntax is
no where near as complex as learning .NET was coming from the unmanaged
world. I think it's well worth the time and nowhere near as difficult as
one might expect.
 
The learning curve depends on whether not you are familiar with OOP. If
you
are familiar with the C family of languages syntax then the learning curve
is reduced even more. Outside of that, it will take a concerted effort to
get up to speed
Click to expand...


My only programming experience is vb.net.
 
Not all that hard. You know VB.NET. You already know a great deal about
the CLR and the System namespaces. 90% of everything you do will involve
the framework far more than it will involve language specific things.

There are a few things to get used to, especially if you've been using the
VB-specific features designed to make it easier for VB6 folks to make the
transition. I wrote in Visual Basic for many years (starting using it at VB
for DOS 1.0). For me, it was easier to jump from VB6 to C# than it would
have been to jump to VB.NET, because I needed "different things to be
different" and VB.NET was just different enough to be frustrating.

My only bit of advice, jump all the way. Don't write 90% of your code in
VB.NET and expect to master C# in 10% of the time. Go ahead and spend a
couple of weeks writing ONLY in C#. Once you get the hang of it, you can
mix them together, but at first, use C# exclusively until you get used to
the differences.

The syntax is not that hard to learn.

--- Nick
 
Yes, C# is the answer! Programming's a breeze with C# and Visual Studio
..NET ... wheeeee!!!
 
Back
Top