A lot of things have been said in this thread - a few points

First of all Clean Code - http://pluralsight.com/training/courses/TableOfContents?courseName=writing-clean-code-humans&highlight=cory-house_writing-clean-code-humans-m9-stayclean*2!cory-house_writing-clean-code-humans-m7-comments*9,5!cory-house_writing-clean-code-humans-m8-demo*2,15!cory-house_writing-clean-code-humans-m2-principles*6#writing-clean-code-humans-m9-stayclean

A good reference book http://www.amazon.com/s/ref=nb_sb_ss_i_1_7/188-8370969-1119167?url=search-alias%3Daps&field-keywords=c%205.0%20in%20a%20nutshell%205th%20edition&sprefix=c%23+5.0+%2Caps%2C323

Set up a Continous Integration system ( Version Control and automated build with unit tests) a VM will do

>OK, I am considering throwing in the towel. I have decided to give dotnet a try. I have read several books about C# and VB#, and I believe that I will be able to write some code relatively fast. But I don't want to start in the wrong end, I want to do it right from the start, so I ask for some advice.
>
>First of all, I have Visual Studio 2012 Professional installed and running on my computer. I also have MS SQL server 2012 installed and running. And I will focus on C#.
>
>One of my first questions is, should I use Windows Forms or WPF Forms?
>
>In VFP I have sub-classed all the base classes, some of them more than one level. Should I do the same in .net also? If so, how?
>
>Can anyone recommend a good book (or two) with essential but not too much reading?
>
>Are there other important decisions I will have to make early in my learning phase?
>
>And last, please don't mock me! I will always remain a VFP lover, and I know that I haven't always written nice things about dotnet. From now on I will avoid writing negative about dotnet until I know better what I am talking about.