Rating: - Nice, but not complete at all
This book is really nice, and i do use it, but especielly the lack of a index is a pain in the royal ... Also, there are to many things missing. And yes, i know it is a pocket book, but still. But OK - i use it a lot so ok book, 4 stars if it had with an index.
Rating: - Wonderful reference, but ...
I agree with the other two reviews I've seen on this book so far, but I have one thing to add: the book would be easier to use if it had an index. Other than that, the book is just right.
Rating: - Small Concise: A Great Reference
If you want to be fluent in VB.NET and C# this 139 page reference is a "must have." The author contrasts the two languages clearly and quickly. Note: This is a very nicely written quick reference, but is not a textbook. Nevertheless, I wouldn't be without it!
Rating: - Another great Pocket Reference from O'Reilly
I noticed before writing this review that someone had recommended "The .NET Languages: A Quick Translation Guide" instead of "Converting VB.NET & C# Pocket Reference". Having browsed through "The .NET Languages: A Quick Translation Guide" at the book store, it is certainly a good book, but there is nothing "quick" about it. At 400+ pages it's really more of an overview and less of a "quick translation guide".
If you are looking for a truly pocket sized conversion guide between C# and VB.NET, I would strongly suggest Jose Mojica's "Converting VB.NET & C# Pocket Reference". This book is in contrast to some of the larger "overview" style books, as it is a reference guide weighing in at around 100 pages. The book is great for developers that have a fair grasp of VB.NET and/or C# and don't want or need lengthy instruction, but rather a quick alternative to searching the .NET help system or looking for code examples on the web.
The format is very straightforward and simple. Every topic includes a brief, but concise explanation and is enhanced with occupying code examples. The code snippets, in most cases, almost speak for themselves. Often the examples are in a rapid-fire "here's what it looks like in C#, here's what it looks like in VB.NET" style. Typically, the topic or keyword being covered will appear in the code in bold, adding to their readability and usefulness.
My only complaint with the book is that I had expected to see an appendix section with a keyword comparison similar to the ones found in the .NET help. It would have been convenient to those of us too lazy to print that section out ourselves.
Overall, this is the best book I've seen if you are a developer looking for a quick conversion reference when working in a mixed C#, VB.NET environment (which could include just about anyone working with .NET today).
|