Where to start to get into .NET programming

[vetteguy]

I have some experience in several "classic" type languages (Visual Basic, COBOL, C, Java, etc.) Other than the little bit of Java I haven't done much with OO stuff. I want to get into .NET programming. What should I start with? Should I do some work with OO languages? Learn XML or ASP? Any suggestions? Basically I'm feeling overwhelmed by how much I don't know and I'm not sure where to start.

 

[KB]

Yes it can get very overwhelming, particularly with a new product that does away with alot of the things you had experience with. I recommend you buy a copy of Visual <your language of choice> .Net and start learning the IDE. Once you have that down, learn the language syntax, OOP and then study the framework classes. By far the best way to learn is to do something fun. Try to think of a program you can write and start searching the documentation for how to do it. The best website to go to for information is www.gotdotnet.com.

 

[joohang]

GotDotNet

MSDN Library

If your OOP is not so strong, you might have some learning curve to overcome (like I did). XML is not necessarily required so don't spend too much time with it. Just understand the basic concepts of XML and how to apply it to your applications.

And KB is right. Writing a sample app is a great way to learn. There are also tons of books out there. Make sure that they are written for the release code, though.

 

[kylef]

I have yet to see a very good book on .net yet, however. Caveat emptor.

 

[BuckleDownBen]

For VB.Net, the book by Balena that is coming out in the end of April should be the best. His book on VB6 was very good, if that is any indicator.

 

[Descartes]

I read a few C# books when I was learning .NET and there were so many errors in them that I couldn't continue. Personally, I find the .NET documentation itself to be lucid enough to read. It does not, however, discuss OOP as a book would, and as joohang said, that is at times a steap learning curve when assimilating all that is .NET. If you have a background in OOP, the documentation should mostly suffice. Other normal avenues of knowledge acquisition would include: newsgroups, mailing lists (DOTNET mailing list), local user groups, etc.

Just jump into it head first, eventually you'll surface.

 

[Workin']

You might want to rummage around here.