Enter your mobile number below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
Getting the download link through email is temporarily not available. Please check back later.
To get the free app, enter your mobile phone number.
A Programmer's Introduction to C# (Second Edition) 2nd Edition
Use the Amazon App to scan ISBNs and compare prices.
There is a newer edition of this item:
Excel 2016 For Dummies Video Training
Discover what Excel can do for you with self-paced video lessons from For Dummies. Learn more.
Customers Who Viewed This Item Also Viewed
Top Customer Reviews
For my money, this is as good as writing gets when the subject is THE LANGUAGE, PERIOD. The writing style is lean, focused, and rigorously accurate. While you might not take it to bed with you, you'll turn to it over and over when you're actively stuck on a concept and want to get it right and OWN IT.
A careful reader could gain all the confidence they need by reading this book first, and then Troelsen's *C# and the .NET Platform* (also an Apress book; no, I don't work for them). That's not to say that there aren't other gems out there (including Liberty (O'Reilly; download the latest version of the code!) and Robinson et al. (WROX; generally excellent, but some chapters are SO BAD, and the typos are EVERYWHERE). But if you have a limited budget and can stay focused, Gunnerson and Troelson (in that order) are all you need.
Gunnerson is very clear at what is good C# style and what is not and why you should choose one idiom rather than another. Also, unlike Liberty's book, Gunnerson leads you through the process involved in developing (including adding multithreading) a serious application where Liberty's samples are much smaller and much less interesting.
The downside is the order Gunnerson chose for his topics is strange whereas Liberty 's order is much more straightforward and traditional and I think easier to understand. Note that people coming from a VB background will have an even harder time with Gunnerson than Liberty. (People with this background should probably choose Archer's Inside C# book from Microsoft Press.)
Summing up: Buy both books if you can, if not buy Liberty's book for a pure tutorial and buy Gunnerson to learn C# style plus how to develop a serious multithreaded application.
What about C# itself? First off you can get the language free as part of the .NET SDK from Microsoft's MSDN web site, it's a command line interpretor like the one in the JDK. Then use your favorite editor to create C# code.
Next, although C# certainly bears a family resemblence to Java it has some truly unique and exciting features that make it the best language yet. For example, it is the first language in the C/C++ family to handle versioning. (For experts the fragile base class problem is gone.) There's also cool stuff like automatic conversion of value types to objects and back again and little things like == doing what it should for strings.
All in all this is a great book that I highly recommend.
The author does not have a strong grasp of Object Oriented programming. It is very clear that he has little understanding of interfaces, which are a vital part of C#. The reason I say this is that in every code example I see, he explicitly "casts" classes references to interface references, when one is not needed (He states that this is required on pg. 80 that you must make a "cast", which is incorrect. Amazingly, he contradicts himself on pg. 128 when he states the "cast" is not needed). There are so many errors in chapter 10 (Interfaces), that I would highly recommend that the chapter be skipped entirely. His section on problems with "name collisions" on pg. 86 is so wrong that it is pitiful. Perhaps at the time the book was published, interfaces in the language spec. were pitiful and the author's examples were correct, but I doubt it. These are just some of the many examples used in this book that are either completely wrong, or highly discouraged. Others include using the term "overload" when the author clearly meant "override" (big difference!).
Although I do like the author's style in trying to explain things, it doesn't help much when his understanding is incorrect. I have found that reading the "C# Language Specification" and "C# Programmer's Reference" (although dry) to be a much better use of my time. Note: I did read the 1st edition. I can only assume the author has fixed many of his mistakes in the 2nd edition, which might make this book a decent intro. to C#.
Most Recent Customer Reviews
I am an intermediate C++ programmer who hadn't been programming for a few years.
While i disliked how he went into some pretty advanced inheritance topics first and then... Read more
This book was recommended to me by a colleague as an introduction to C#, but I have to say I'm a bit disappointed. Read morePublished on January 4, 2005 by sjm
Easily the best C# book on the market. If you want to learn the C# language (as opposed to an introduction to OOP or . Read morePublished on December 17, 2004 by deko
This text has the possibility of being really good. The author obviously has some fresh ideas on how to structure and present Yet Another Language Text that does not follow the... Read morePublished on August 8, 2004 by Jan Moren
Eric Gunnerson, A Programmer's Introduction to C#, 2/e (Apress, 2001)
The title of the book pretty much tells you all you need to know, though it might better have been termed... Read more
This is a great introduction, for programmers, to the C# language. To get the most out of it, the reader should have a familiarity with programming and object-oriented concepts. Read morePublished on April 9, 2004 by Eric Kassan
I bought this book a while ago. Days when MS announced C#, I wanted to get my hands on a book that can give me a head start. I saw this one in the market and bought it. Read morePublished on December 25, 2002 by D. Kapoor
to me was best of all the books, doesn't waste time teaching you what oop is, just teaches c#
a pleasure to read, good code
There are lots of errors in this book. Some errors are even the
syntax errors. Maybe becuase of the version problem? I don't
know. I am using Beta2. Read more