That would be a logical choice... except for one thing - When you have seen a few versions of the framework pass by, you understand how the "new" features in each version have evolved from previous features. (For instance, the evolution of delegates in C#)
This conceptual understanding makes a developer exceptional. Although it is quite possible to find a book or tutorial on C# 3.5 that details this particular aspect, it would be rare indeed. On Feb 13, 5:10 am, Cimpy <[email protected]> wrote: > I do not agree with others. I would go with last stable version > (framework 3.5, using visual studio 2008) or the candidate new (visual > studio 2010, But you will find less examples and articles, and those > that you can find might need changes in the final release) for reason > that if it were true that it does not matter when you go after c#, > then get the last, and in case you could always decide to step back if > you need. By the way, it is not true "it is the same", unless you > work outside Visual Studio Ide: the integrated developement > environment is grown up, and things are both a little bit easier and > more numerous than before...
