5 comments about Professional SharePoint 2007 Development (Programmer to Programmer).

1. I have read many SharePoint books and indeed this is one of the best. The topics have been covered in great detail. The book starts of with an in introduction to the Microsoft Application Platform and how SharePoint Server integrates into the Platform. It then goes on to cover the various features of the product and how to develop applications using those features. The chapter I liked most was the "WSS V3 Platform Services" which covers in detail creating site definitions, custom field types, features, solutions and web parts.
   
   If you are developing SharePoint solutions I suggest you read the book



2. I always find WROX books are the best value for money. This book is no exception. The details this book provides is atypical and that is what I find very useful. Devil is in the details and we need that for programming.
   
   If you are interested in Solutions Development on SharePoint Platform, this book is a very good companion.



3. Working on a few projects I needed to find some good Sharepoint 2007 reference books. This book is excellent with the examples it provides and the way they authors explain it to you. Very easy to understand, clear and concise.
   
   I do however wish they had more real world examples like for example when working with events in sharepoint they would show you how to retrieve the id's from the list lookups when assigning to another list programmatically, or how to change the permission of a selected item for a selected specific group or person, or access active directory.
   
   Other than that, it is a good book that will help you get along your way.



4. I was given this book by one of the Author (John Holiday) during a training on Enterprise Content Management. I have collected quite a few books on SharePoint most proclaiming to be a developers guide but they have chapters after chapters devoted to configuring WWS 3.0 or MOSS. However, this book gives you a very good start and provides step by step guide on creating various solution.
   I would recommend this for all beginners and intermediate developers!!!



5. The book is good but the source code of Chapter 13 is missing.
   It's very frustrating to learn a new technology and see problems with the source code.
   Wish the authors can take time to check the source-code is uptodate before releasing a book, or at least put it for download after complaints.
   If the authors can update the source code, it will be great.
   Otherwise a good book.

5 comments about Learning Python, 3rd Edition.

1. After getting a review copy of Learning Python, 3rd edition, I had forgot how much really great material was in the book. If you are interested in learning about Python 2.6 and Python 3000, and have some experience with Programming in another language this is an excellent book.
   
   This book is not a reference book like the excellent Python Essential Reference, but more of a example driven guide through features of the language. I would pick this book up even if you know Python, as it covers new language features that have not been documented in some books.



2. This book was very handy as a reference when having to learn python in depth pretty quickly, only gave it 4 stars because it didn't go deep enough in a few areas for my taste but I keep going back to it now and then and I'm glad I have it on my bookshelf.



3. If you are a top-down learner this book is not for you. You can safely pick "Dive into Python".
   However, if you are the bottom-up type, you will not regret. While the Python slogan promises "one way to do it", Mark Lutz will show you four, and explore every detail, like complex list comprehensions, closures and the diamond inheritance pattern. This is why you will wait 200 pages (exploring data types) until the introduction of the first Python statement, and 200 pages more for the first script.
   But if you cross the details, you will get excellent understandings of the core Python logic, which will save you countless debugging hours in the future.
   The OO part alone worth the entire book. It's going from the very basics of OO programming up to elementary design patterns and some advanced OO implementation issues in Python.
   One last caution: although 600 pages, this book should be really read cover to cover. It's a true tutorial, which gradually develops the major concepts (sequences, assignments, references, objects, namespaces etc) from the ground up, with (midterm?) exercises. Give yourself a few hours to really learn, exercise your brain (and fully grasp 100 ways to silently override your variables with namespace mistakes). It's a great book.



4. I'm talking about the 3rd edition. It's the first book about Python that I read, so I can't make a comparison. It may be just the best first book out there, but I'm not impressed. The book reads like a draft, not a book in its 3rd edition. The author just keeps repeating himself on minor points in subsections back and forth. It's 700 pages long, but I wish it were half the length, after cutting needless elaboration and repetition. Perhaps the older editions are more concise. On the other hand, we readers may not have a choice.



5. Python has the reputation to be a language that is easy to learn. Well, why do you need a book more than 500 pages to only learn the language then? The answer is that even if you can learn the basics very fast, it has a lot of bells and whistles that can take time to master.
   
   This book covers only the language not the libraries, but covers it very well. Highly recommended reading once you'll want to use the language to write something bigger than a script of 10 lines.
   
   4 stars only because I would have expected some exposure to the standard libraries as well for a book called "Learning Python"

5 comments about Design Patterns: Elements of Reusable Object-Oriented Software (Addison-Wesley Professional Computing Series).

1. Being a total noob to programming, my friend got me into learning about Objective-C and Cocoa. I have bought many books on the subject and I'd like to say that this book helped me with my understanding of objective-c programming language.
   
   Thanks to the authors



2. Contents of Disign Patterns are more and more classical in software engineering. The work is unaguable the basis which lead to a growth of design patterns. This particular issue is a high-quaulity hardcover on heavy paper, and good print. Its an issue for all who like to have a personal library of important book in superior quality. Well useful are the two bookmarks available in the robust binding.



3. This is a great book on design patterns. Not only does it cover the theory of what each pattern is and it's respective use. It also gives very concrete examples of the proper use of each pattern in C++. I highly reccomend this to any serious programmer.



4. Most of the books I have read about object oriented programming were about some specific language and failed to provide a more general way to think about solving problems without writing a lot of code. This book was a missing link for me and I wish I had read it sooner. The authors provide you with elegant ways to use object oriented language features to simplify your programming solutions.
   
   When the specs on your project change and you have to re-factor your code, you may be able to use a design pattern from this book to simplify your solution and make your design more flexible with regard to the parts of the spec that are changing quickly.



5. unlike the last pattern book i reviewed (see my other reviews), this one has an attractive cover. i like blue.

5 comments about Essential ActionScript 3.0 (Essential) (Essential).

1. Great book, well explained, very complete on all topics... in my opinion a must for all flash-developers. Even if there might be chapters you might want to jump as an experienced professional, this book is the perfect reference to sit on your desk and help you out when you don't know or don't recall some issue or maybe want to know the most accurate form of doing something.



2. Excellent. This book was recommended to me by a colleague, and I can't recommend it enough.
   
   As a C# and VB.NET programmer, I had plenty of experience to jump into the middle, but I found myself enjoying the early chapters so much that I decided not just to skim them, but to read them as carefully as the rest of the book. And in doing so, I was rewarded with tidbits of information that I would have otherwise missed.
   
   Anyone who wants a thorough understanding of ActionScript 3.0 would find this book incredibly valuable.



3. I mean in actionscript 3.0 you define variable as var x:int = 10 not var x = 10; that makes me confuse that it will deviate from standard later in book so why to continue. But like the style which is good for beginner who is not good at OOPS...



4. As an interface designer I've been working with Macromedia products since 1992. I feel that regarding the interface aspects of designing and producing a multimedia application the products have just devolved over time. I'm glad that Macromedia is no longer around and hope that Adobe will do better on this aspect.
   
   Actions Script 3 is just the last nail in the coffin of my relationship with this products: how can it be that at this point in time it take this book more than 600 pages to get to a level were you can actually move a movieclip on the stage? Were are the introductions to the readers that come from ActionScript 1 and 2 to at least make it easier for them to get up to speed?
   
   I think that Colin Mook's other books on the subject are good-the Actionscript 2 one was very good- but the amount of work that this one ask of the reader and the level of abstraction of the language truly trumped all my attempts to actually getting anything done.
   
   At more than 900 pages this is a heavy burden to carry around, but no electronic version comes with the book. I had to download one from bittorrent ,even though I bought one here in amazon, just to be able to search thru it and have it always with me. in the end the book is just sitting on a shelve collecting dust, I rather work in actionscript 2 for the time being.
   
   Spend your money elsewhere unless you already work with OOP at a fairly advanced level ( JAVA for instance): you will make a better investment in paying someone to code for you if in a hurry.
   
   Boy how I miss Mtropolis!



5. If you have a good background in Computer Science and you are brand new to ActionScript and Flash in general you will be frustrated.
   
   If you want to use Adobe Flex Builder (free for 90 days) and you go by this
   book then you'll find that none of the examples in Part I will give you anything, but an idea. If you want to evolve the discussed example you'd have to wait till Part II. Meaning by the time you get to do anything you'll loose any desire to evolve any of the examples from part one.
   
   I prefer to evolve the discussed example so I can remember it.
   For example Reader exercise on page 211, tell you to first read Part II of the book to come back and actually do it. That means I have to suspend my ongoing learning (including my desire) and skip ahead. Annoying.

5 comments about Head First Design Patterns (Head First).

1. I buy quite a bit of stuff from Amazon. Don't we all. But all this while, I had never wrote a review. Just never felt compelled to do so until getting this book.
   
   Just awesome!
   
   I'm a hobbyist programmer and never learned about design patterns in school. Understanding they're importance I tried learning. I really did. But everything I read from articles to glances at different books just left me more clueless.
   
   Except for a very small minority, this book will blow your mind (in a good way). I now understand why there are patterns, what the most popular ones are, and how to apply them.
   
   Just get it.



2. It's really wonderfull. Not only funny to read, the most important thing: you learn a lot with it.
   If you know very much about patterns and object oriented design you may find it useless... but even then you'll admit it's a great book for beginners and for people (not only beginners) who's been working with Java (or other OOLanguage) but haven't learnt subtle details. It makes you realize how many things can be always done better. It takes enough time to explain everything well. And finally, it doesn't only teach patterns but a bit of OODesign in general.



3. The "Head First" book series is the best product that O'Reilly makes and Head First Design Patterns is a perfect example of the quality and innovation inherent in this great series.
   
   If you only need to learn the main design patterns or if you want to find out what the deal is with this whole 'design pattern' thing then this book is the easiest way to get started. For those who need to know all 23 design patterns then you might be stuck with the famous "Gang of Four" book which is not as easy or entertaining as this book but good none the less.



4. The promise they make on the preface of the book is true. The knowledge really sticks to your brain, part due to the examples and part due to the language the authors use along the text. Just one thing to record, the authors were too humble declaring it can't be considered a reference guide, yes it is, although fun, the book is an excelent reference guide.



5. Finally, a book that explains the basic design patterns, in Java, in a way that makes sense.

5 comments about Learning ActionScript 3.0: A Beginner's Guide.

1. I'm plugging away with Learning ActionScript because I can see how it's capable of amazing things, and I have been using Flash for a little while.
   However this book is written using the kind of language that seems simple to a programmer and obscure to the rest of us - a lot of what is written I simply can't fathom despite frequent re-reading (I'm afraid this probably says more about me than the writers of the book). It's probably best for those who are more familiar with the composition of scripts and want to upgrade to ActionScript 3. Not really a beginners guide.



2. Any computer library strong in web development titles in general and ActionScript in particular will want the beginner's guide to Flash, LEARNING ACTIONSCRIPT 3.0. It's an excellent introduction which also lends well to classroom use and assignment, covering all the basics of how ActionScript and Flash work and surveying logic, content, transferring projects to ActionScript, waveform visualization, loading HTML and more. Chapters offer hands-on exercises to reinforce skills building learning and also pair well with a companion web site offering material for all the exercises plus test quizzes. ActionScript learners will find it an essential - and surprisingly easy - reference.
   
   Diane C. Donovan
   California Bookwatch



3. I'm surprised a book by O'Reilly was released with this many typos. I've been going through it and typing the tutorials that were new material for me. The amount of mistakes is just unacceptable, especially that many times it happens in code. The code is correct in the examples from their web site which begs the question, why didn't they just cut and paste it from the WORKING examples? The errata on their web site has a few of the mistakes but I've found many more.
   
   Anyway, apart from the ridiculous number of typos it is a pretty good book. I don't think its the be-all Flash book like some people on here that have been raving, but it is a good stepping stone book to learning some OOP. Its very practical and eases you from timeline code into classes. Most Flash books seem to go all timeline or all OOP, so good job to them for understanding their audience. Another knock I have is that in many examples they try to show you additional techniques apart from the main thing they are trying to illustrate. Normally I would applaud this because you just learn more, but too often here it just confuses. My last issue with the book is that it sometimes fails to explain an important element of code or give you a really vague explanation, even if that is the purpose of the exercise! Personally I want to know why I'm typing every line in so I can be more flexible when I write my own code, as opposed to blindly memorizing and hoping I remember it when I need it.
   
   All in all, you won't go wrong with this one, but it is by no means perfect. It could've been great. Its not. But its still good and worth a purchase.



4. After reading the other reviews I decided to give this book a try and I don't regret it.



5. First, please note that many of the 5-star reviews are written by experienced Flash professionals, who already have actionscript expertise -- and that makes them poor judges of how clear this book will be to a beginning audience.
   
   The book is explicitly written for beginners, but the authors often have a good grasp on what readers know. On one page they start talking about "trapping" events. What does that mean? Who knows?
   
   I have a good math background, so I was able to decipher the math chapter, but it contains explanations like, "A radian is the angle of a circle subtended by an arc along its circumference that is the length of the circle's radius (hence the name, radian)." What's the point of writing a sentence like that? Will it be understood by anyone who doesn't already know what a radian is? Has a math newbie even ever heard the word "subtend"? This casual use of undefined jargon happens in every chapter.
   
   Also, sometimes they're just wrong. They say that a ball moving 4 pixels to the right and 4 pixels down per second will have a velocity of 4 pixels per second in a south southeast direction. No. The Pythagorean theorem (which they explain, badly, in the next section), says the ball will be moving more than 5.6 pixels per second. And the direction is southeast.
   
   The book really is full of typos, and they're not all caught in the errata. It's necessary to go the website and download the code being discussed in the book. The files you download will have the correct code (though before you check the code, as you're reading the book you're thinking, "Do I not understand, or is this code wrong?") Unfortunately, the book sometimes refers to these files by the wrong name, so you have to figure out which file to open. That's really inexcusable -- how hard would it be for the authors to go to their own website and correctly name the files?
   
   Another random, infuriating example of the book's sloppiness: on page 144, the authors state a line of code "g.curveTo(275, 0, 400, 100);". In the context of the chapter, the hardest part of this code to understand is the "275, 0" and it's the one part they don't bother to explain!
   
   And as long as I'm ranting (I just threw the book down to come and write this), the authors often put unnecessary lines into the code. I'm left trying to figure it out, wondering, "Why did they put that there? Is it necessary?" so I try the code without the extra material, and it still works fine. But the authors never explain why it's there, so while you're trying to learn to read actionscript, wanting to understand the importance of each line and its relationship to the rest of the example, you're thinking, "Am I just missing the importance of this line? Or does it have no importance?" Learners shouldn't be left to wonder those things!
   
   It's a maddening book, full of unexplained terminology (I just found the phrase, "dedicated canvas"; huh?), incomplete explanations, bloated code, and many, many errors.

5 comments about Pro LINQ: Language Integrated Query in C# 2008 (Windows.Net).

1. This is a great book for learning LINQ. Lots of code examples, fairly exhaustive and does well at explaining concepts. However, the first chapter must have been given special attention knowing it would be the sales pitch for the book. The rest of the book falls into a more rushed fashion, evidenced by typos (mostly in code), and sometimes condescending tone. Also, if there are two extension methods with the same signature, and one has the word Descending tacked on the end, please don't take another four pages to describe its usage. LINQ to Entities is not covered at all, and they don't claim it is, just a heads up to the potential buyer. All that said, this is overall a great book on the subject, but it could use a little polishing.



2. I agree with all of the above positive reviews. Excellent book. I just wanted to comment on the publisher. This is my 3rd book(my other two were a book on WPF and C++/.Net) published by Apress and they have all been very good. I don't know if that is just dumb luck but they do an excellent job.



3. Microsoft must be under new management, we are getting a slew of new, truly useful tools that are making pretty big strides forward for faster more enjoyable C# development and ease of maintenance. The latest technologies seem well worth taking the time to master. I find the combination of LINQ and the Sync framework couldn't have come at a better time. While the book mentions that LINQ to SQL only supports SQL Server, that is no longer true as you can also use (at least) MS SQL Server Compact Edition 3.5 (which is required for the Sync Framework). You can't use the visual object relational designer with SSCE but the book documents SQLMetal, and you can use that to create your context.
   
   Overall I found this to be a very good book but it has a few flaws. If like me you are interested in LINQ for a current or upcoming database project here is what I would suggest. First don't start with this book, finish with it. Start with the ten excellent screencasts by Mike Taulty. Then read this book. Your reading will go much faster and you'll get a satisfyingly sated feeling. The author will probably hate me for saying this, but if you already know SQL or ADO.NET 2.0, I would suggest reading Chapters 1-3, then skim 4 and 5 just to get an overview of the operators available. Then read part 5 (Chapters 12-18) on LINQ to SQL. After you digest that I would suggest whichever topics interest you the most, then I would finish with a more thorough read of Chapters 4 and 5 on Deferred and Nondeffered operators, which in my mind are really a thoroughly documented reference section.
   
   The reason the author will hate that, is he doesn't want readers to use LINQ for just database purposes, and he states that many times in the book. In fact, I think that is why he put the LINQ to SQL section at the end. However, he seems to have made a significant effort to make any part readable on its own, so I see no problem with skipping to the end so early.
   
   The book doesn't really cover data binding, but there is a lot of good information on that available on the internet (the above mentioned screencasts show some of them, and an overly long video on Channel 9 with Young Joo from August 2007 shows even more).
   
   I also have a few nit-picky things that drove me crazy. The most significant one being the amount of repetition and unedited console output. I was also none too happy that the author didn't mention that the Visual Studio Command prompt was under the START menu not an IDE menu. But then again without the author I wouldn't even have known there was a Visual Studio 2008 command prompt.
   
   The weakest part of the book is the index, it is downright anemic. In the several weeks since I've finised the book the index has NEVER helped me find things I remember reading. If you find items of interest you better pencil them into the back cover if you want to find them again later. If one book ever needed a free PDF, this one is it, but they charge $10 for it. Maybe that is why they made the index so bad, to encourage you to fork over another $10.
   
   That said, I also found a good half-dozen or so gems in the book that saved me significant time. Now I could tell you what those are but I think you should buy the book to find out.



4. This book is very well thought out. The author helps you understand some subtleties of relational algebra (without really saying it) and helps you think like a LINQ head. It's a different way of doing things, but he shows that if you get a basic understanding of a handful of concepts you can grow it from there.
   
   awesome book!



5. No doubt about it. If you are learning/using LINQ, this is THE book to have. Author did an excellent job explaining the material and giving numerous examples, that work, about the material. Had to mention the "that work" part as I get so frustrated when I buy a book and the examples do not work. I could tell this book was a "labor of love" and he didn't just crank out a book to make $.

5 comments about Head First Java, 2nd Edition.

1. 
   
   That's what the "Head First" philosophy seems to purport, and the foray into their lingua franca (Java) is a prime example. From the start Sierra and Bates break down the essence of "whole brain" learning a potentially dry subject like programming and design in the Java language. They then apply this methodology to each chapter by framing core instruction with cute sidebar humor and illustrations and then concluding with review exercises in the form of puzzles that openly appeal to the right-brained audience. Such a shift in the paradigm of computer science instruction has been scoffed at by many, but the truth of the matter is the new generation of developers are those who have an affinity to agile-dev, elegant-syntax type technologies such as Ruby or PHP, those who are learning from the avant-garde likes of the "Poignant Guide to Ruby". For Java evangelists extraordinaire like Bert and Kathy, making the sacred core language that much more accessible only made sense. That being said, I would caution the droves of aspiring young webmasters (not to mention migrants from older high-level languages) to understand that even with the "connect the dots" activities besprinkled throughout some assumptions about programming competency are made by the authors. In my opinion, this would not be an exclusive venture into the world of Java (and it's a BIG one) but a supplemental text that spawns the "aha" moments when more condensed and comprehensive texts like those by Cay Horstmann just don't drive a critical point across. I can say that I do appreciate the authors jumping immediately (erm, head first) into OOP concepts.
   
   In sum, I would say that this book is not for everybody, but for those that need a healthy diversion from the "standard" reference material (read: Java API).



2. Basically the book was ok. The difficulty I had was when I paid for Expediate service, I was expecting 2-3 days for delivery, not five days. and when I requested the tracking# and name of delivery company. All I got was the order# which did not help me at all. I will not order from this company again.



3. The style and manner of presentation of the new HEAD FIRST Book Series is a great way to learn these newer languages. Highly recommended for everyone.



4. I am an instructor who was tasked with teaching a basic Java class even though I didn't really know the language. I had to learn it FAST. I looked at a lot of different Java books and this is the one I settled on.
   
   The style of the "Head First" books is unconventional and may seem silly on the surface but it is based on serious metacognitive (thinking about thinking) principles and IT WORKS.
   
   The book is fun but it makes its point. It is also a comprehensive and well-chosen coverage of the subject. Java is a whole universe and they have made a good call on what to present and what to leave out.
   
   This is my first purchase from the "Head First" series and it won't be my last.



5. This book is for beginners but it assumes that you know the basics about computer programming, I mean, it won't teach you what is a program, what is code or those very basics things. If you have programmed in C, C++ or C# then this books could be slow for you but still useful but if you don't know about those languages or Object Oriented Programming then this book is great to learn OOP and JAVA, really good.

5 comments about Code Complete: A Practical Handbook of Software Construction.

1. I started by reading the first edition of this book. I got the second edition when I was almost finished with the first edition of this book.
   
   After getting the new version of the book I decided to continue reading the old one because I found that there are quite a few differences between the old and the new edition.
   
   This is perhaps one of the best books that I have ever read on programming in my life. The author Steve McConnell has put together a book that is independent of what ever programming language that is used. In the authors words. He wanted to write a good book on software construction because he had looked around and had not found any good books out there on the subject. I would have to agree with him there are not a lot of books on good programming technic. There are hundreds of books on this programming language or that programming language.
   
   Code complete is so good that I feel every programmer should read it. It would be best if in the first year of college every single student read the book. I just don't know how it could fit into a regular curriculum. Even if it does not fit that well into a regular curriculum what is taught in this book is probably more important then what most people learn at school.
   
   I like the book and would advise it to anyone that programs.
   
   I am looking forward to the new edition because the old book didn't have much advice about object oriented programming. Mostly because it was a new way of programming when the book was first written and he didn't want to commit much information to it when object oriented programming was so new. He does talk a little about things that are outdated but the book is still one of the best.
   
   I will wait a while before I read the second edition but I expect to be as satisfied with it as I was this one.
   
   Great book that should be in every programmers library.



2. it's a book that all programmers must to read. it explain a lot of interesting things about how to made good software!



3. I'm currently studying computer science and have been reading this in my spare time. Skip your lectures. Just read this book! If you want to construct software in a timely, efficient, and complete manner--this is the definitive book to read. Not dry at all, Steve McConnell covers topics for all experience levels. Even if you're an experienced programmer, you will learn something from this great piece of literature.
   
   I've only gone through the first few chapters thus far. So pending finishing my reading, I'll update this review. Unfortunately this might never happen as I find myself re-reading portions of the book to pick up new ideas and details for software construction!



4. If you're an experienced software developer or a newbee in the world of commercial computer programming this book will give a good kick in the right direction. Steve McConnel will keep you hooked by mixing the right guiding concepts with real-life knowledge and examples.



5. This was a great book both for me and my team. I've been in the software industry for many years. I started building a team of developers and needed an easy way to bring novice and experienced programmers together on a similar set of standards. This book provided us with the perfect framework from which to start our team. We've developed several major projects using the principles in this book and have experienced a great deal of success.
   
   One warning, the book gets a bit tedious after the first half. If you're looking to improve your C programming skills, it gets really detailed into pointers and other fun, or not, stuff. Also, the examples are in VB.NET...but you still get the point.

5 comments about Pro C# 2008 and the .NET 3.5 Platform, Fourth Edition (Windows.Net).

1. Andrew Troelsen has done a remarkable job. The book
   does a great job of explaining C#. Every time I had a question about a specific topic he would answer it with in a few pages. This is not a reference book. It is a book that through thoughtful text and coresponding examples leads you through C#. It is an intense book and every word and example needs to be examined so don't expect an easy trip. Pro C# 2008 and the .NET 3.5 Platform, Fourth Edition (Pro Series)



2. It's a great book for an experienced programmer who already knows Object Oriented Design and Programming, because many important concept (like inheritance and polymorphism) are explained very briefly.
   But if you come from Java, C++ or any other C++-derived language, you'll feel familiar with the concepts explained and begin developing in C# quickly.
   The development tools explained are principally Visual Studio 2008, but also some other IDE and compiler are explained.
   Maybe a little disappointing the examples, and some suggestion of exercises at the end of each chapter would be very usefoul.
   Anyhow, 4 stars.



3. This is a book that I'd expect from Apress pro series. As a java developer, I've had no prior experience with .net. This book has walked me through and tought me the .net concepts and the c# language in no time. Very straightforward, no blabla, and thorough. Also with 1300+ pages and being hard-cover, it is a bargain. Highly recommended.



4. Ho trovato un'ottima guida in questo libro. Gli argomenti trattati sono spiegati in maniera eccellente: breve introduzione, esempio banale e poi una trattazione approfondita dell'argomento. Un breve sommario conclude ogni capitolo e permette di fare un ripasso di quello che si e' letto all'occorrenza.
   
   E' un libro che consiglio sia a chi inizia per la prima volta a programmare in c#.net (seppure sono necessarie delle basi di programmazione oop) e naturalmente ai piu' esperti, pubblico a cui sembra essere destinato.
   
   Devo dire che ho trovato in questo libro un fedele compagno di lavoro, visto che e' corredato anche di un ottimo indice analitico e, per chi lo acquista subito, dell'intero pdf full searchable.
   
   Mi assumo la responsabilita' di consigliarlo a tutti :).



5. I would wholeheartedly recommend this book to anyone who is serious about learning C# and is coming from an older .NET platform or from previous C/C++ experience. The book is extremely thick, yes, but wastes little space. The examples are detailed in explaining the topic at hand but do not carry extraneous details that could distract from the current topic.
   
   I would also recommend this book to anyone who might not have constant access to a computer to test out the topics. I find this book to be one of the few programming books that I can sit down with in front of the fire and read without having to get up every five minutes to see how an example really works. This book manages to fully explain the topics in such a way that the explaination is complete; a visit to the computer to try and understand the text is rarely needed.