Books are a waste of time.. The only time I'll buy a book is if the info is very difficult to source online.
If you can read C++, you can read C#. The class naming and hierarchy of their APIs are so verbose that you should be able to understand any sample code.
If you're not in any projects (open source or not), get in & hack hack hack away. C# is pretty widespread now so any issues, just Google it. If you don't like MSDN doco, learn to like it, because it's free and pretty good once you know how to navigate it. And there are a truckload of MSDN blogs as well.
Who are you planning to be employed by? You might be better off learning.NET 3.0 (WPF, WCF and Workflow Foundation) since it's where Microsoft want to go... however corporates will probably give it a few years before it becomes more mainstream.
Slashdot Mirror
Echo the 1st reply..
.NET 3.0 (WPF, WCF and Workflow Foundation) since it's where Microsoft want to go... however corporates will probably give it a few years before it becomes more mainstream.
Books are a waste of time.. The only time I'll buy a book is if the info is very difficult to source online.
If you can read C++, you can read C#. The class naming and hierarchy of their APIs are so verbose that you should be able to understand any sample code.
If you're not in any projects (open source or not), get in & hack hack hack away. C# is pretty widespread now so any issues, just Google it. If you don't like MSDN doco, learn to like it, because it's free and pretty good once you know how to navigate it. And there are a truckload of MSDN blogs as well.
Also look at: - http://msdn.microsoft.com/msdnmag/
- http://www.apress.com/free/ (Dissecting a C# Application on the bottom - is about SharpDevelop IDE, which is pretty good)
Who are you planning to be employed by? You might be better off learning