I was expecting a more detailed book on VS 2005, but it wasn't. However some people might find this book useful.

I received this book within a few days and the book was in great shape. Nice job.

Too much of this book has no depth and is repeating what is written on the screen.

Try as hard as I can, I cannot find a purpose in this book other than for the authors to make some money. It barely touches on the options in VS2005 without any concrete direction or in-depth description of why to use the features. I have found that the VB2005 book I purchased at the same time as this ("Visual Basic 2005 : The Language") provided much better coverage than this book
I would NOT reccommend this book to anyone. You would find a much more effective use of your money by buying the above book or a book on the targer language in VS2005 you are using

Try as hard as I can, I cannot find a purpose in this book other than for the authors to make some money. It barely touches on the options in VS2005 without any concrete direction or in-depth description of why to use the features. I have found that the VB2005 book I purchased at the same time as this ("Visual Basic 2005 : The Language") provided much better coverage than this book
I would NOT reccommend this book to anyone. You would find a much more effective use of your money by buying the above book or a book on the targer language in VS2005 you are using

Yes this book is riddled with typos and coding errors, but it's still a very well written and informative introduction to VB 2005.
The chapters are really easy to read (not like normal textbooks), with solid examples and small end-of-chapter exercises to reinforce ideas.
If it had been properly proofed, it would easily get 5 stars.

Microsoft's Visual Studio 2005 is an enormous product. It is Microsoft's standard and proposed developmental platform for virtually all programmers. It's basically an IDE (Integrated Development Environment) on steroids. That means it starts as a text editor so that you can type in the programs you are writing. Added to this is a series of help menus, debugging aids, and other things to assist you in writing programs. After you get your program written, then there are additional tools that will assist you in running the program, tracing the flow control, putting in breakpoints, etc.

Being Microsoft, the main emphasis in Visual Studio is Visual Basic and Microsoft's C# while other languages are covered to a somewhat lessor extent. This book does not cover the languages themselves. It's a full size, thick book just on the IDE itself.

But on the IDE it has everything there is to know about using the IDE. Especially helpful are the authors comments on various third party add ins you can get off the web, often at no cost.

The last chapter in the book is on the Visual Studio Team System which talks about using Visual Studio to manage geographically distributed software projects that may be in development all over the world at once. While this chapter will give you the fundamentals, there is another whole book on using Team System. You'll just get an introduction from this book.

Professional Visual Studio 2005 fills an important niche: it is for experienced developers who are new to Visual Studio and need an explanation of the environment and all of its features. The book fulfills that need reasonably well, but it is important to understand what you will and will not get from it.

What it does well is to explain the environment and the general approach to development that underlies all of the key aspects of Visual Studio. This begins with the structure of the IDE and its options, then proceeds through a vast tour of Visual Studio concepts, .NET framework fundamentals, various parts of the development architecture (such as security and database connections), an introduction to other features such as developing for devices and team services, and moderately in-depth explorations of important topics such as debugging and deployment. As such, it serves as a combination of a general overview and a concise manual.

Of particular value is that it describes and exposes many features that one might otherwise overlook. Visual Studio 2005 is a huge, complex piece of software, and there are capabilities and options (for everything from IDE options to XML to automation) that are not apparent at first.

What it does not do is to address the aspects of Visual Studio that are specific to individual languages. As is appropriate for a book for experienced developers, it does not present much code or "how to" examples. However, it would be helpful if it discussed more of the differences that affect development in languages besides C# and VB. There is a consistent emphasis on those languages and the [...]
It also presents only minimal tutorial aspects. Although the general steps are described, there are not detailed walkthroughs of such steps as how to compile, build, and debug programs in a given language. It would be nice to have a few chapters on such topics as "porting Unix C code to Visual Studio", or "Moving from Borland C++ Builder to Visual Studio". Those are not critical omissions, but would be nice for some readers. Finally, the book is primarily about the usage of VS from the point of view of individual developers; it focuses mostly on the "professional" version, not on the specific enterprise/team capabilities (which are briefly covered in one chapter).

In short, this book is a good, comprehensive conceptual "manual" for Visual Studio 2005, especially for VB and C# developers. However, there is still an unfilled niche for a book on "Visual Studio 2005 for C++ Developers".

Professional Visual Studio 2005 is an exceptional book. It is not often that you encounter a book of this kind written with this kind of clarity and thought.

To the previous reviewer, I would suggest that you read the book before reviewing it, rather than just looking at the pictures. If this is how you judge all of the technical books that you look at, then it is little wonder that most if not all of your book reviews consist entirely of scathing remarks.

However, it does sound as if you have done an exhaustive study on Australian developers to determine that they are all sub-standard programmers. I guess it must be hard for us, when we all live in tin sheds in the outback, coding on our primitive workstations made out of kangaroo skins and old Fosters cans. I would say that your "experience" with Australian developers is more of a reflection on your company's hiring policy or the standard of whatever technical forums you frequent, rather than a reflection of the technical experience of an entire country.

In short, this book is a great book for anybody wanting to know about Visual Studio 2005, and the previous review should be ignored.

First, I did NOT buy this book, only came across it in a bookstore while trying to learn a few details about the new visual studio compilation system.

I guess every serious developer knows most Wrox books are junk, but still can't believe they managed to publish such a stupid and worthless one.

It's even worse than a simple rehash of the MSDN online documentation, which would at least save you some time to search through it.

The table of contents said it all: 56 chapters in 900 pages, most of which are made up of boring screenshots. Do the math and you'll ask yourself the question: who are the targeted readers?

These 56 chapters covered every aspect of .NET: C#, VB, ASP.NET Web development, Windows Forms, Team System, Debugging, Macros, Refactor, Compact Framework..., in a very very very poor and shallow fashion.

So the next thing i did was to find out who were the authors, and there you are: two experienced/accomplished but "Australian" developers. In my albeit limited experience, the majority of Australian developers were shallow in their understanding of highly complexy technical stuff, and they write code in an exremely sloppy fashion. But these two guys are supposed to be the creme de la creme of .NET developers in that country, or maybe not?

In any case, next time you buy a book make sure where the author(s) are from first.