Programming Books

Very useful for someone who wants to learn to use Unix on the Mac and has prior knowledge of command line languages.

Mark G. Sobell and Peter Seebach's A PRACTICAL GUIDE TO UNIX FOR MAC OX S USERS is a reference the UNIX/Mac user simply must have at hand: nearly a thousand pages of reference material on everything from basic and advanced shell programming to Mac's OS X filesystem and utilities modules make this the best reference on the market for users who seek either a step-by-step tutorial or a basic browser's reference for problem-solving. Exercises to test knowledge boxed highlights of information make it easy to either refer to for at-a-glance troubleshooting or sit down and study for step-by-step methodology.

This is the book I've been looking for. Not just 'OS X for Unix Geeks' or 'OS X in a Nutshell', I wanted more. As much as possible, in one resource. 1000+ pages signaled a big yes.

I have yet to read it all the way through, but so far this is a very good guide for those who want not only to learn the general 'Unix way' of computing, but dive under the surface of OS X and examine its specificities in the command line interface, aka the Terminal (/Applications/Utilities/Terminal)

No, this isn't a 'hacks' book, and there's no mention of rsync, for example, but you'll find ample documentation of the underside of OS X--there's a lot more to it than just a GUI, folks.

Educational, yes. Hence 'Practical Guide'; you'll learn a good deal, in almost textbook fashion. Recommended to enhance the power and fun of your OS X experience!

I have several of Mark Sobell's Unix based books and this one is as good as the others which are all excellent. You don't nessecarily need all of them but they are truly tailored to the platform and are a quick way to get to what's important when a new platform presents itself.

If you want to know the underlying MAC, this is for you.

I got this book as someone who had used UNIX before, but this was many years ago, and I had forgotten a lot. This book is great for picking up the functionalities of various UNIX tools - the explanations are clear and concise. It also works very well as a quick reference. The bulk of the book is devoted to bringing you up from a potentially zero-experience user to someone who can work with ease with editors, shells, and more. Simple examples are included throughout. The back of the book has a 250-page command reference section for quickly looking up how to use a particular command. You could read the whole book and progressively work with UNIX as a self-taught course, or just reference the sections you need.

Very readable and highly useful book. One major hit. It is ironic that the author complains about the symbols in other books. For queueing he invents his own, instead of sticking with standard practices. This is very fustrating to readers that have other books on queueing and need to compare.

The book is well written and "user friendly". As Dr. Gunther said during a class I recently attended which is based on this book, "You will not look at performance analysis the same after taking class." -- or reading the book. He was correct ... I don't. My views have changed for the better.

The only mark against the book I have is it doesn't have an example section (with answers for each example as an appendix) at the end of each chapter to help people apply the concepts they learned reading the chapter.

The author provides good practical coverage of queuing concepts and then goes on to show how to use queuing models.

I found it interesting that he gives an example of typical computer time periods scaled up to human proportions. If a computer clock speed in nanoseconds were analagous to seconds then a main memory access of 100 cpu cycles would be like some minutes and a disk access would be like some months.

His coverage of queuing concepts is very accessible with a minimum of math.

Scalability is frequently discussed concept that often is not very well quantified. He has the most original approach to quantifying scalability that I have seen.

A queuing modeling package called PDQ is also provided with the book. The source code in C is provided for the PDQ package.
There are some PDQ examples within the book. This is a real bargain because certainly the PDQ software is worth much more than the cost of the book.

If you have and interest in capacity planning and performance analysis (especially if you work in this area) this is a must have book.

If understanding and managing computer systems performance is in your job description and you can only buy two books, this is one of the two (the other is Raj Jain's, "The Art of Computer Systems Performance..."). Neil Gunther's book is not just another tome on queueing theory. Immediately useful methods and formulas are presented in the context of real problems. The two chapters on instability in systems and scaling of multiprocessor systems alone make the book worth its price. Readers need to know that there is some math in the book (there is just no escaping it) and that some of the cited vendor products are becoming dated. The Web site associated with the book contains many items of current interest, an errata sheet correcting minor errors in the book, and downloadable programs related to performance evaluation.

Although this book's full value will be realized if you understand the C programming language (he uses source code it illustrate points throughout the book and provides a C library for performance analysis on the accompanying disk), anyone with good math skills will gain much from this outstanding book.

The core approach is Performance By Design, which is aligned to product development. His approach, if used properly, will ensure that performance goals are established in the design phase, and are met as a system or software evolves through the development life cycle.

Highlights of the book are:
(1) Through introduction to the foundation of performance: queuing, parallelism and multiprocessor systems.
(2) Coverage of contemporary issues, such as client/server and web system performance,
(3) Unexpected forays into performance characteristics and considerations that I've encountered in no other book. For example, Part 3 of this book addresses subtle issues such as transient analysis, scaling behavior and similar topics. Here the author integrates theoretical physics into performance analysis - while this may seem odd, it only reinforces that much can be added to the performance analysis body of knowledge by drawing from sources outside of computer science. His qualifications for this material includes a Ph.D in theoretical physics, and his ability to clearly explain concepts that are foreign to the average computer scientist or performance practitioner is excellent.

I like the conversation style that the author employs, the way he starts with the basics and builds upon them and the thoroughness in which all aspects of performance are discussed. More importantly, although advanced math concepts are introduced the way they are presented can be understood by anyone with high school or college freshman knowledge of probability and calculus.

We as users of the PSM with years of experience in the quality and measurements world tend to over complicate the measurement system we develop. This book is a yardstick and is a good tool to ground you when you are creating the measurements. It keeps your mind in the more simple and effective road to resolving the issues. Remember the old saying, "Keep it simple stupid (KISS)!"; this one helps guide you to accomplishment of this goal.

This is a good solid presentation of the subject that gives a good overview of the several types of approaches to measurement. While I would prefer that the subject matter also focused on software engineering as well, it does a good job of what it was created to cover.

This is a good read for anyone thinking about employing metrics for software projects. I have read several books and articles on metrics, software and program managment, in the last 6 months and this one of the few which was worth reading. Text is easy to read and the message and methods are presented in a straight forward manner. No, you will not find any amazing breakthoughs in software project managment in this book. What you will find is a good foundation for adding metrics which add value to software program management.

There is a wealth of material available from the PSM site, including the PSM Insight application and PSM Guidebook. However this book is not redundant because it is structured as a clearly written introduction to practical software measurement, that includes excellent guidance for implementing it into your organization. In addition, the 304 pages that comprise this book manages to convey the information contained in the existing PSM documentation, and does so much more succinctly.

I found the most valuable parts of this book to be the clearly described measurement model, and the way the authors distinguish between data that is useful to projects and organizational data collection and analysis. This material places PSM in context and is a sound starting point for an organizational SQA initiative.

The case studies reinforces the mechanics of PSM, and also contain advice and pointers for implementing enterprise-wide measurement. Although I've been following the PSM initiative almost since its inception and have read all of the copious materials available, I still gained much from this book. If you're establishing an SQA function or striving for CMM level 4 or above you'll find this book invaluable. The URLs provided will lead to even more material, including a free Windows-based software tool that fully supports the practical software measurement process.

I would rate this book ****** if it were possible. If you are looking for material on how to start a "software metrics program", look no further. This is the ultimate reference on software measurement initiatives. The PSM method is compatible with the CMMI (Measurement & Analysis Process Area) and the foundation for the ISO/IEC 15939 standard. All of the authors are recognized authorities in software measurement and process improvement. Dr. Barry Boehm (COCOMO author) has written the foreword. The PSM process is sponsored by the DoD and the U.S. Army. The book itself is comprehensive, well-written, and easy to read. It provides ready-to-use templates such as "Measurement Construct Template", "Project Measurement Plan Outline", and "Data Verification Checklist". Chapter outline:

1 - Measurement: Key Concepts and Practices
2 - Measurement Information Model
3 - Plan Measurement
4 - Perform Measurement
5 - Analysis Techniques
6 - Evaluate Measurement
7 - Establish and Sustain Commitment
8 - Measure for Success
Appendix A - Measurement Construct Examples
Appendix B - Information System Case Study
Appendix C - Synergy Integrated Copier Case Study

Note: Appendix A provides 14 detailed, complete examples of measurement constructs ("metrics"). Appendixes B and C provide 2 comprehensive case studies (approximately 60 pages).

It would require at least a 2-day workshop to address all the information provided by this book (probably at 10 times its price). You can't afford to miss it if you are more than casually interested in software measurement. Hope you enjoy it as much as I did.

Any project one can undertake is not necessarily going to be like all the others. "The Principles of Project Management: Run Projects on Time and To Budget Using This Simple Step-by-Step Guide" is an informed and informative handbook for managers in charge of making their projects the best they can be with proper planning, strategy, and beginnings. With advice on warning signals to help people stay on the right track, "The Principles of Project Management: Run Projects on Time and To Budget Using This Simple Step-by-Step Guide" is a top pick for community library business collections and any would be project leader.

This is a short book, but it's packed with useful information about project management. It neatly avoids getting bogged down with PM jargon, instead cutting to the core concepts. It's not designed to get you through a project management qualification (though it might help!), but will certainly help you to become more efficient at managing projects, which at the end of the day is what *really* matters. Aimed at people who want to get projects done, even if they're not officially 'project managers' within their organisation.

The book is broken into five sections - what project management is (and just as importantly, what it isn't), getting started with projects (covering the who, what, where, why and when of project initiation), getting the project done (tools, best practice, project control), the essentials of good project communication, and finally following through - closing off the project.

Rounded off with appendices covering essential project tools, templates, and links to useful software apps, this is a great book for people starting out in project management. And whilst not strictly aimed at experienced project managers, I'm sure that everyone will find something useful to take away.

Great stuff.

Do you find yourself responsible for executing projects and need some guidance on how to get the job done? If you do, then this book is for you! Author Meri Williams, has done an outstanding job of writing a book that shows you how to get projects completed and delivered on time.

Williams, begins by explaining why Project Management is a difficult thing to do effectively. Then, the author explains why leading teams, managing schedules and implementing ideas, takes a lot of focus and hard work. Next, she gives advice on work styles and issue tracking. The author also discusses why stand-up meetings are very difficult to prepare for. She continues by showing you why closing on handling is a total disconnect. Finally, the author discusses how to measure operational success, ongoing support and maintenance.

This most excellent book aims to lay out defined steps to get projects done right and on time. But, more importantly, the author designed this book for people who are working on larger projects by themselves.

'The Principles of Project Management' is one of those books that does nearly everything right in my eyes. A small footprint (204 pages = don't say more than you need to), fantastic design, and good writing and content. It's no secret that sitepoint is one of my favorite technical publishers out in the field today and nearly every one of their books gets 5 stars from this reviewer.

This book is no different.

Project Management is a difficult thing to do and do effectively. Managing schedules, leading teams, getting ideas to fruition all takes a lot of hard work and focus. To be a good project manager you have to wear all sort of different hats and it's a daunting task. Like salespeople, if you are a great project manager you can have a lot of success and a lot of times it's the kind of skills that can't be taught, but are ingrained inside you.

But you can make those skills stronger no matter what level project manager you are.

From Gantt charts to tables to delegation, estimates, and becoming an amateur psychologist working with your team, this book is one of the best inros to becoming an effective project manager. You will learn all the necessary skills to be successful and have fun while learning.

If you are an experienced PM you owe it to yourself to read this quick book and if you are newbie this should be required reading. Great content and ideas + a great design make for an outstanding effort and book!!

***** HIGHLY RECOMMENDED

I don't usually work as a project manager, but I've been in enough projects to recognize most of the pitfalls described in this book.

The book provides a good, common sense approach to project management. Some of it may be overkill for smaller projects, and some of it may not quite cut it for really huge projects, but for anything inbetween it's a worthwhile resource.

I enjoyed Meri's relaxed style of writing (although she uses more exclamation point than one usually expects from a fully sane person :)). The way she shares her personal experience makes her advice all the more credible.

After reading the book, I felt like taking over a project I'm involved with at work, just to put it back on track again.

This is by far the best book available on DNS. It is very informative and yet the reading style is entertaining (not fluffy though). Overall, it is a joy to read. The author is able to communicate effectively to both the expert and the novice. Look no further than here for a great DNS reference book. Way to go Ron Aitchison!

After reading several of the chapter sections at the authors website, I needed a bit more understanding about how to install and configure Bind 9 onto our Windows box. I wanted to use Bind on old hardware running NT4. I fired off an email to the author and got several pointers that fixed the problems I was having. I realized the pointers he had given me were all covered in his book. After purchasing the book, I not only found out lots of stuff about what all the parameters are but also discovered how to manage bind over the LAN in a secure way. This book is a must have for anyone that wants to use Bind 9 for the first time. It has helped me several times already.

The Domain Name System is a critical component of any large network or any computer connected to the Internet. While a home user would not need to setup a DNS server, business networks of any significant size would benefit from an internal server, DNS caching router or other components. This book takes the reader through a very good explanation of DNS and BIND, how it works, how to set it up, how to test it, and how to troubleshoot it. There are many books on DNS and BIND but most either assume a certain level of prior knowledge, provide theory without implementation information, or provide implementation information without any theory so you have no idea how to troubleshoot a problematic implementation. Author Ron Aitchison does an excellent job of discussing both theory and implementation in this book so you end up with a thorough education. He even covers the implementation of a secure DNS server. This book actually takes the reader from a level of complete novice through advanced DNS administrator and does an excellent job of it. Pro DNS and BIND is highly recommended and one of the better books on the subject available.

Ron Aitchison's Pro DNS and BIND packs a whopping 550 pages of material which is easy to read for the novice or ongoing DNS administrator, and which is very well written (I greatly enjoyed the author's style). After a short introduction in which I learnt some interesting facts about the provisioning of the root servers, the author implements a first zone describing the necessary concepts such as resource records, queries and zone transfers very clearly, followed by the different types of DNS setups (master, slave, caching, forwarding and stealth servers); these are covered in depth in chapter 7. Chapter five covers IPv6 and its relevance to BIND. Throughout the book, references to other DNS server implementations are given, but the primary focus is of course BIND 9.3.0.

Aitchison leads the reader through detailed installation of BIND on Linux, FreeBSD and even Windows (ISC has an installer for Windows in its portfolio), after which common DNS tasks are discussed (how to delegate a subdomain, how to define SPF records, etc. read it on-line here) as well as a chapter on tools.

The third part of the book is dedicated to securing DNS configurations with topics ranging from simple administrative issues (chroot jails) through securing DNS updates and zone transfers with TSIG and DNSSEC.bis which is covered very extensively in chapter 11.

Chapters 12 and 13 provide extensive commented references on BIND configuration and Zone files. There is of course plenty of on-line reference information on these two topics (including the author's very good DNS for Rocket Scientists) but I like to have reference information on hardcopy (in the event my DNS servers fail, and I can't reach the on-line documentation :-) )

In part 5 the author shortly covers programming with the BIND API and the resolver libraries, and he follows that with an interesting chapter on DNS Messages and Records, good to have if you want to sniff your way through DNS traffic.

The publisher's web site carries a sample chapter as well as the source code to the book which is also available in TAR format on the author's web site together with complementary information and pointers to further resources.

My only complaint about this otherwise excellent book is that on two or three occasions I read a paragraph that I thought I'd just read before; some duplication must have taken place (or I was tired). For the next edition, I'd like to read a chapter on interoperability between BIND and Microsoft Windows DNS servers, specifically regarding DNSSEC.

This book is an absolute must have for anybody who needs to understand DNS in the first place (irrespective of the implementation he or she plans to use), and it is a must have for a systems administrator who is either intending to deploy or has already deployed BIND 9.3. I wish I'd read this book before the first mentioned above.

while the reference from Paul Albitz/Cricket Liu is sometimes hard to read and long winded, this text from Mr. Aitchinson covers everything and yet stays very clear and simple. I could configure and start a caching only DNS server in less than 30 minutes (well, after omitting the first few introductory chapters ;-). If you want to look up sth., there is also a big reference section. There is also an errata-page at:
http://www.netwidget.net/books/apress/dns/notes.html

I also found this book *much* more useful as the first, because of the fact that it is much more up-to-date!
I can recommend this book to everyone, who
*) wants to install/configure/start/maintain a DNS server
*) wants to get informed about the Domain Name System in general

Up to now, this book is really an insiders' tip!!

I have read several books on this topic, but this book was very structured wich made it easy to follow. It gave a very clear explaination on both base- and advanced OOP programming concepts. Many things I'v not read anywhere else and many times I yelled 'AHA!' and 'WOW!'. Yes, it was great fun to work trough all the 'Fun with...' examples.
I really can recommend this book, however NOT if you are a beginner!
I also learned that I'm a Generic Type, because I drink a lot Of T. :)

This book covers what programmers need to know. The pillars of OOP are presented and clear examples are shown.

I refer to this book often because it gets to the "meat" of things rather quickly and is not for beginners.

My only criticism is that this book's examples are 90% console applications. Nobody uses this in the real world. But I understand the focus is on the code, but I still like the Deitel approach better. Use Windows applications NOT console, take the time to get the screen shots. (Just my opinion).

Don't get me wrong, I can easily translate over what he is trying to convey, but still I see great authors such as Francesco Balena showing most examples with the console window. I don't like this trend. But hey that's me.

Very good book though..

This is best VB.NET I ever had. This book explains OO concept very clearly with easy to understand examples. I am still in middle of the book. So eager to finish till end. Waiting to read more books from this writer. Thanks for Excellant Work.

This book covers just about everything: The .NET platform; VB language fundamentals; OOP; Assemblies and classes. In each chapter the author gives a simplified example and then progresses thru to a complete module. He explains each step in detail and give many of the most-likely errors.

This is not novices. The author expects some level of programming experience with VB, C, C++ being the best. It is also best for a Visual Studio 2005 environment, though it is not required. If this is you and you are looking to move to VB.NET, this book is absolutely for you.

If you are looking for a Visual Basic book that covers a lot more than books like Wei-Meng Lee's Visual Basic 2005 Jumpstart than this book should be at the top of your list. As well as the basics this book is very good at explaining advanced concepts like Interfaces, IEnumerable Types, Generics, Asynchronous Delegates, and Multithreaded Applications. The author has an excellent writing style. He stays on track, does an excellent job at expaining complex concepts, and provides a lot of hints about how the topic he is writing about now is related to the big picture. Apress should also be commended for the graphical layout of the book. It is very easy to find information on a particular topic in this book as all of the book is divided into clearly labeled short sections.

I had little knowledge on the subject of AJAX, but this book enlightened me. I could scope out the capabilities of this technology by reading a few key chapters. Now I understand the AJAX used in the enterprise level application I now maintain, plus a lot more. If you're a .NET programmer, I think you'll like the way this material is presented.

Matt and Dan's ASP.NET AJAX book is an excellent one. It is packed with useful content, and contains a lot of great code examples that demonstrate real-world usage examples.

The book covers all of the core ASP.NET AJAX Scenarios:

- Server-Side Controls (UpdatePanel, UpdateProgress, etc)
- Client-side libraries
- Networking Stack
- Application Services
- AJAX Control Toolkit

Matt Gibbs is the development manager of ASP.NET at Microsoft, and led the ASP.NET AJAX 1.0 development team - so obviously knows his stuff well. Dan Wahlin is a great trainer and presenter of ASP.NET and ASP.NET AJAX. You are in very good hands with them.

I highly recommend this book.

Very well-organized, easy to follow and provided a great starting point for the ASP.NET AJAX framework. Even if you've been surfing the ASP.NET AJAX documentation you'll still pickup some good tips and information from this book.

I have nearly completed my first tour through the book. It is well-organized, written with considerable clarity, possesses a reasonable number of focused examples, and covers ALL the bases in good depth, including deployment and custom controls. Some very minor deficiencies are a scattered few forward references and a muddling of the details of JSON serialization when accessing web services, but the errata and future printings will hopefully clear these up soon.

Thua I strongly recommend it as the FIRST book to introduce yourself seriously to mainstream AJAX 2.0.

Just got a copy of this new book on ASP.NET AJAX and it looks great. It should be because Matt is the Development Manager for ASP.NET so he deeply understands the product. He has also worked on several other books and I can personally attest to the fact that he can indeed form complete sentences. ;-)
Seriously, this book is straight from the source and contains good, detailed information about the ASP.NET AJAX release that applies equally well today and in Visual Studio 2008

Arsenovski has done a great job with this book. It is clearly written, easy to follow and very practical. A great one to keep on the shelf and reference as needed. The free tools that he covers in the book are a bonus! They really help to get you applying what you've learned quickly.

I highly recommend this book for any .NET developer, not just those who use Visual Basic.

Not a typical Wrox title, generally these tend deal with specific technology in "no-nonsense" fashion. This book has more theory in it and is not technology specific, you will find it valuable if you program in just any version of Visual Basic .Net and any type of application. Not likely to become obsolete very soon, since basic premises of refactoring will continue to be relevant even in upcoming versions of VB.

I am working with group of developers that came to VB .Net from VB6. Currently we are in process in improving the way things operate using some agile stuff. The overall disposition is pretty good, team has already been formed and things like daily stand-ups, client involvement or short iterations are generally welcomed by all. However, when more technical, code level stuff is discussed, there is more discussion (if not opposition). These folks pack years of experience and will not accept that you can teach them their job just like that. There is no way you can force things like unit testing or refactoring. You have to be able to hold your ground and answer all the questions with some good arguments.
This book gives you in-dept view of refactoring with a lot of practical, code examples. This means that you are well prepared to answer any uncomfortable question. It builds up gradually, so it is easy to follow.
Almost every chapter ends up applying the stuff that was just exposed on a sample application with a lot of code. Surely author spent a decent time on this title. You can download the code and see it progress from chapter to chapter. This gives a great insight since you can read and debug the code at the same time and not just some toy or isolated example.
Here is chapter to chapter break-down of the book.

Chapter 1
Intro chapter, defines refactorings end code smells and explains the kind of baggage VB carries because of its origins. Cool section on misinterpretations, this will prepare you for some tough questions that might come from uninitiated developers or managers.
Explains the importance of writing simple, comprehensible code. For example:
Dim oXMLDom as New DOMDocumet() vs Dim portfolio as new DOMDOcument.
The first statement gives you no idea of what first DOMDocument represents, in second it's the portfolio, and if you know the application context you will know what to expect.

Chapter 2
Teaser chapter but also good single-chapter sample of some typical refactoring work. Captures well typical process of development of VB applications. Starts out with few event-handling methods, ends up with number of domain classes and some inheritance thrown in.

Chapter 3
Chapter on refactoring tools, also gives you some insight of how different tools like refactoring add-ins and unit testing framework fit the big picture of agile development process.

Chapter 4
Intro chapter on application that is used to illustrate refactorings throughout the book. Explains the business case, requirements, lists some use cases. It is important to understand the context of the application to be able to follow-up on refactorings. Also some funny stuff here, like freshman developer that takes pride in copy-paste development.

Chapter 5
In-dept discussion on Static vs. Dynamic and Strong vs. Weak Typing that is rarely dealt with in such depth. This is basically controlled with Option Strict and Option Explicit options. If you program in VB, you must be aware how these work out.

Chapter 6
Chapter on error handling, especially legacy vs. structured error handling. Again, something everyone should know, but rarely explained in such depth. Cool stuff is step by step recipe for converting legacy to structured.

Chapter 7
Deals with some core refactorings like Dead Code Elimination, Scope Reduction etc. It's like cleaning up your code for some serious refactoring stuff.

Chapter 8
First step in structuring your code is getting serious about the problem (or business) domain. Also explains Rename and Safe Rename refactoring, talks about Interface vs. Abstract class, Open-Closed principle etc. some serious OO stuff.

Chapter 9
Some core refactoring stuff. Teaches you how to eliminate duplicated code and why it is the worst thing it can happen to your code. Explains Extract Method and Replace Magic Literal with Symbolic Constant variable. Nice and simple example based on circle geometric shape on how procedural design is transformed to Object Oriented design (Module and Shared method rings a bell?)

Chapter 10
If only method extraction would be as simple in real life... This chapter goes further with method extraction and deals with some common problems like temps.

Chapter 11
Where do objects come from? How you design classes? Some core OO stuff in this chapter, including Extract Class, Move Member (Method or Field) refactorings, smells like Database Driven Design or Data Class, Large Class, OO principles like Single Reasonability Principle etc. Lot of stuff and handful of pages in this chapter.

Chapter 12
Build upon previous chapter. Deals with inheritance, polymorphism, genericity. Explains the difference between class and interface (or implementation vs. interface inheritance), difference between delegation and inheritance and criteria to chose one or another, list some common misuses of inheritance etc. Again, a number of refactorings like Replace Inheritance With Delegation or Extract Interface, Extract Super etc. Some heavyweight OO concepts in this chapter, takes a time to digest.

Chapter 13
Explains what is important when taking a birds-view of software. This chapter is especially important for software architects. Talks a lot about dependencies in software and why you should minimize dependencies in your code.

Chapter 14
Single chapter for huge subject, still a lot of material covered. Design patterns are the most advanced subject in OO, so refactoring your code in order to make use of patterns is in no way child's play. Mostly deals with creational patterns. First mention of Dependency Injection in some VB book I come across. Now taking into account that Unity application block [...] has been released in April, this is really cutting edge stuff!

Chapter 15
Talks about latest VB improvements that come with VB 2008. Starts with XML enhancements like XML literals and then the rest is about LINQ. Explains a LINQ implementation called LINQ-to-SQL. This is first Microsoft Object-Relational Mapper (ORM). Again, cutting edge.

Chapter 16
If you still deal with VB6 code, than you know that migrating to .Net is no easy ride. This chapter explains some techniques that will help you migrate your code and make it .Net in sprit, not leaving it crippled by simple migration that will only make it execute in .Net. VB6 lacks inheritance, generics etc, so you need refactorings to make it VB .Net.

This book has no real competition as far as I know, no book on refactoring or agile for VB .Net developers. The one that come close is Agile Principles, Patterns, and Practices in C# (Robert C. Martin Series) but it is for C# developers and requires a lot higher starting point.
When other books come up, I am sure Professional Refactoring in VB will continue to hold its ground. Highly recommended!

Really great book on refactoring. Although it is based on Visual Basic examples, same advices can be applied to C#, Java or any other OO language.
Martin Fowler finally has a fair partner on my shelf ;).

First of its kind for VB.Net developers. While it does not contain a complete catalogue of all known refactorings, you get a thorough study case used throughout the book, tooling, how to use refactoring for upgrade of legacy VB6 code, a chapter on VB 2008, some important object oriented principles and even short intro on refactoring to patterns.
This book is deep and takes a while to digest. However, it's not about showing off some irrelevant academic knowledge. Author is not afraid to mention "Dependency Injection" or "Single Responsibility Principle" but all of these are demonstrated to be relevant and get illustrated through very practical and real-life examples.

Has some great tips and examples for doing some things fast. The code samples are good, concise, and point you in the right direction even if they don't show you a direct solution.

Great book, alot of useful tips/tricks for any level. Also clear and easy to follow.

I have learned lots of little tricks from this book and recommended to other SAS programmers. I have about 3 years of programming experience and this covered some techniques for tasks that we not obvious to me. I enjoyed his other book as well.

An excellent, information-packed and well-organized book that's definitely worth the purchase price and would be a good investment for experienced and novice SAS programmers alike.

I agree with the previous reviewer, especially on the point that the book could benefit SAS beginners, not just the more seasoned programmers: it is clearly organized, and makes it easy to look up the topic of interest.

I bought this book knowing VB but was new to R/3. Within days I had a working interface to SAP. If you want to use COM objects to connect to R/3 and make remote function calls this is the book. Great examples on using late binding too if you want to put the functionality into a dll without having a control bound to a vb form. Of the many computer books I've read, this is one of the best.

Details with examples. Good for all SAP R/3 tools and application developers. Explains BAPIs, RFCs, bussiness object repository (BOR), SAP DCOM Connector component etc.

"Professional VB SAP R/3 Programming" - demonstrates how to combine existing Visual Basic tools with the new extensibility tools, so that you can develop robust enterprise applications based on SAP R/3 from a non-SAP programming environment. It also explains the fundamentals of SAP, including the new SAP tools and technologies. SAP R/3 business objects and BAPIs are implemented and a guide to the SAP Business Framework is illustrated. The SAP R/3 Automation tools are used to replicate SAP functionality from VB and the DCOM Component Connector is used to generate business object proxies, aswell as programming the core components of the DCOM Component Connector. Browsing the SAP R/3 Business Object Repository is demonstrated and working code samples of both inbound and outbound SAP R/3 operations are included...

An excellent guide for understanding BAPIs and RFCs, complemented with good explained VB programs which are useful for learnig how to develop interfaces whith SAP using VB.

I'm not a VB programmer. I obtained this book to better understand how BAPI's worked and could interface with external applications based on a project team demand to develop better masterdata loaders. The first three chapters alone are goldmines of information that are neatly tied together and explain the concepts and framework used. After reading them I understood why SAP went this route and better understood some of the potential areas where BAPI's could assist our development team. The latter chapters get into more VB oriented issues but are useful regardless of VB experience (or lack thereof). Our VB developers all own this book.