Is c# players guide outdated? Or should I still learn from it? What if I'm using a newer visual studio then 2012?
Date: 22 Dec 2014 07:59
Number of posts: 9
RSS: New posts
Also what's the crash course? Should k try it after I read the book?
I think Emblis's comments sum it up pretty well.
As the author, I wanted to throw in a few of my own thoughts too.
The book's focus is on the C# language itself, with less information about using Visual Studio. Since C# 5.0 and Visual Studio 2012, there have been no changes to the language itself, and very few changes to the .NET Framework. (There was a 4.5.1 and a 4.5.2, but nothing really meaningful or useful to a broad group of people have been added.) So all of the information in the book is still 100% completely relevant, and as far as the language or the .NET Framework is concerned, there's nothing I'd write differently if I were doing it today.
In the fall of 2013, Visual Studio 2013 came out, and I intended on putting out an update of my book (which got delayed for various reasons). The truth is, even with the new version of Visual Studio, basically the only thing that changed was the download location, changing occurrences of "2012" to "2013", there wasn't any real meaningful content differences in the book, and there would have been a lot of work to update screenshots and stuff. So it was really more work than it was worth, and I never got to it with the other tutorials and books I'm working on.
In November 2014 (or was it late October? whatever… just a month or two ago, at any rate) Microsoft made a much more significant change: the release of Visual Studio 2013 Community edition. This is the Pro version, but free to anybody except large corporations. (You're a large corporation if you work for a business that has >250 computers or makes more than $1Million in revenue.) VS 2013 Community allows you to sell what you make, so for all intents and purposes, it makes all of the Express editions obsolete.
That's a pretty big change from what I've currently got in the first edition of my book, which encourages you to use 2012 Express. I'd now recommend Visual Studio 2013 Community.
From a content perspective, as long as you can find VS 2013 Community on the Internet (here is is: http://www.visualstudio.com/en-us/news/vs2013-community-vs.aspx) then there's nothing in the book that you probably won't be able to figure out on your own. The change in the recommended tool is really the only meaningful difference.
Now let me complicate things a bit.
Visual Studio 2015 and C# 6.0 are coming soon. Likely in January or February or 2015. (They don't announce the date in advance, but they've been saying late 2014 or early 2015 all along, and based on the fact that they're on about the 4th CTP, we'll soon see release candidates and the final release.)
C# 6.0 will include a lot of little nice upgrades across the language, and I'm currently in the process of updating my book for this. I'm hoping to be able to launch the second edition of my book the same day that VS 2015 arrives, which means having it ready in advance. Same day release may or may not happen, but it will be coming sometime in the next couple of months for sure.
So while I want to say, "go ahead and buy the book, it's up-to-date except the correct version of Visual Studio, which I've now linked you to," the reality is, while it's up-to-date now, it won't be for long.
Now having said that, it seems like there are a few options.
One is, you could simply hold off on buying the book and use the C# Crash Course for the time being. The C# Crash Course was the beginnings of my C# book, but the book covers twice as many topics, in twice as much detail, and with a whole lot more revisions and editing to make it clearer and better. Plus the book has some features like the Try It Out problems that give you a chance to actually work on C# code, which go a very long way in solidifying the concepts in your mind. The C# Crash Course is a good start (and it's free) but you're not wasting your money with the book.
So you could start with the Crash Course and start working with C#, and then buy the book when the second edition comes out. That's Option #1.
Option #2 would be to just buy the book now and deal with the changes later. There are already a lot of good posts across the Internet about the changes that are coming in VS 2015 and C# 6, and with just a little bit of searching, you could find all the information you could dream of.
Along with that, one of my biggest concerns I had (and still have) when I set out to write a technical book is the fact that it will get out of date before long, and eventually, my readers will be left with something less than perfect. In a lot of ways, and to most publishers, that's just what comes with the territory, and they just tell their readers to just buy the new version of they want.
I could go the route of most other people, but I love the readers I've got, and I want to take care of them. So I don't know how yet, but I intend on coming up with a way to help readers get the latest content. I'm not sure of the details. Obviously, I can't ship a new physical book to everybody who bought one. But perhaps something along the lines of a free PDF update that contains the parts of the book that changed to everybody, or a full PDF/eBook copy of the 2nd edition for everybody who bought the physical book within the last three months, or something along those lines.
Anyway… sorry for the long post. I hope that answers your questions though. You can hold off for a few weeks or a few months, use the C# Crash Course in the mean time, and get the book later when the second edition comes out, or buy it now and get whatever I can figure out for updates when the second edition comes out. Or option 3, which is that now that you better understand the role C# Crash Course, you could just try it out and maybe you don't even need the book… I'm definitely biased here, but I still recommend the book. :D
nah m still buying the book. funny how they say you can finally sell with the community version. everyone sells there programs with like vs2012 etc. Ill be selling programs too with vs2012.
tbh, ill learn the vs2012 with your book and then later on ill grab the newer stuff, cause code is code. It probably wont change significantly. So yeah ill grab the book. Its 80$ here is canada which sucks aha. =/. you know any where i can buy it cheaper?
i over exadurated a little xD. i payed $50 cause like 2 day shipped i guess.
i gotta pay border fees. gonna be a little more for me. Probably $60.
how long do you think it would take me to finish the book and understand it. well everyone learns at a different paste. but any estimate? xD
I'd say it really depends on how much you code. When I got the book, I was brand spanking new to C#, and just coming off a C++ project that about drove me crazy. After the c++ experience, C# seemed to go pretty quickly and I was up and coding within about a month to where I wanted to be. Still, there were some things I didn't learn until several months later because in my coding I just didn't need it or was accustomed to doing things a little differently. (List<> and interfaces for example)
That being said, I think I learn the most from correcting code mistakes. So, the more I'm actually coding and using the theory and new materials, the faster I learn. Also, the more I code the more I learn to make the same stuff more efficient and cleaner. I think between 3 and 6 months is when I became really comfortable and didn't need to ask nearly as many questions. So, if you have previous experience, you should pick things up pretty quickly!
The .NET and the C# Standard have seen a few updates since the release of the book, however, very little to nothing have changed in the eyes of new programmers. If you are new to C# you could probably pick up one of the first books released and almost everything would still be relevant.
Visual studio has also seen a few updates but to the newcomer those updates does not matter much. A few tools may have been moved or expanded upon but I doubt you will notice any difference aside from a slightly different layout and artistic style.
You can start with the crash course right away, it stands by itself and is a good place to get started. If you feel like continuing after having completed the crash course the book is an excellent next step.