Software Books

I looked high and low, and this has to be the best option for developing an LDAP or ADSI component in C++. Find this out of print book and buy it instead of buying another book that is still in print.

Really awesome AD programming book. Covers all the basics of AD and ADSI and then dives into the LDAP API which all other authors try to avoid and dont cover well. You do not need any other AD programming books if you have this one.

Very good book, extensively covers LDAP programming
unlike others.

I've struggled with using LDAP and this explains it all with code samples, which for the likes of makes it easy to learn and best of all Copy and Paste

Really awesome AD programming book. Covers all the basics of AD and ADSI and then dives into the LDAP API which all other authors try to avoid and dont cover well. You do not need any other AD programming books if you have this one.

This book provides excellent coverage of the subject. I found it to be accurate and to contain the details I needed.

This is hands down the best book I have ever seen on the topic of Windows debugging. Whether you are chasing tricky synchronization issues, reverse engineering, or probing for security flaws, you'll do well to have this one handy. A bit pricey perhaps, but worth every penny.

Simple review here:

If you're a developer working on Windows who sometimes needs to debug and diagnose complex / intermittent app failures, BUY THIS BOOK!

There is simply NO other book that delves so deeply into how to debug using WinDBG / KD and it'll be some time until someone creates a book that supersedes this one.

Very well written and containing information that would normally take YEARS to come by on your own, this book will save you MONTHS of hard work.

BUY IT NOW!

If you do nothing more than read the initial 4 chapters you will probably learn something. If you can get through Part II and Part III you will improve your knowledge of Windows programming and good general debugging techniques no matter how experienced you are. This is one every developer should have sitting by his PC.

I have little to add to the effusive praise of previous reviewers. This is a one-of-kind book. An instant classic.

Beware, however. As others have noted, this is definitely an _advanced_ book. If you're not comfortable with arcane command syntax, bits and bytes, and such this will be painful to incomprehensible for you. On the other hand, I dare say you will never be a true Master Debugger until you have a good grasp of this material.

You would do well to start with Debugging Microsoft .NET 2.0 Applications or the now-unavailable Debugging Applications for Microsoft .NET and Microsoft Windows. Both will give you an easier introduction to WinDbg. The latter, older volume has much more information on native code debugging than the newer version. As they also cover the Visual Studio debugger in detail, most developers need go no further than one of these.

Note that WinDbg _can_ be used with SOS and ADPlus to do some pretty fancy .NET debugging that isn't possible with Visual Studio alone. For that matter, the .NET CLR on Windows is implemented using the same Windows API as any native application. I've seen WinDbg used to trace bugs through C# application code down to find that the defect was actually in the CLR or Windows itself. John Robbins (author of the previously mentioned books) states in Chapter 6 of the latest version that "in our consulting work at Wintellect, which as you know works on the toughest bugs, we use WinDBG nearly 70 percent of the time."

Don't ignore this book just because you program in .NET!

Watch out for the font used in the listings though. Not being a master myself, I've been stumped for quite a while because the letter 'l' looks like the number '1' in the font they use. (I've been assiduously following the examples line-by-line).

I also recall being stumped because of an error or two in the text, though I admit I can't find them now. These as you can imagine could be a serious problem given the arcane and undocumented nature of quite a bit of the material. Just make sure you check the errata periodically. Ironically, the errata web page for the book is not functioning at the moment...

Thomas Watson and Charles Spurgeon are my favorite Christian writers, and I never thought I would find another author that I would put on par with them. But J. C. Ryle has now joined my favorites, and his book Holiness is an incredibly rich, valuable, readable resource for any Christian who wants to truly grow in his or her walk with the Lord. Highly recommended.

If you are looking for a solid book, theologically, then look no further. Ryle is an excellent theologian and practical as well. He wants his readers to understand the work of Christ and salvation in the life of a believer. It is great for Bible studies or personal growth.

I would recommend this work to any true believer "working out their own salvation in fear and trembling". It is sound, very comforting and at times very sharp. It is worth every penny and it pays for itself after the first page. Buy it now!!!

The author believes man is Justified byu Faith alone, but believes a Christian Faith is identified by its fruits. This is good, though I do think at times it may seem he believes otherwise. The book sometimes explains something in a thousand words that some may explain in two hundred. It is interesting read considering the book was written some hundred twenty years ago. He complains about easy conversersion without counting the cost of departing from your oldways (sins). That giving life to Christ is not a simple prayer but athoughtful process where you stand before God. He expresses the difference between having more Christians and having less Christians but more devoted. He also disdusses the visible and invisible Church. Those who are members of a local body of Christ but have not truly repented for sins and seek Jesus as God, Savior, and Lord. I found the exposition very interesting at times. A few times I wish he get to the point.

This book is very detailed and covers the subject very well. It is not written in the easy to read style of modern books and demands concentration. Ryle backs up his thoughts with plenty of references to scripture. His thoughts would be in line with the Puritans. The book is both challenging and encouraging.

If I could get someone to write down everything I don't know about LotusScript and Java, it would fill a book. Well, this is that book.

Hatter and Banks aren't wordy and target this book strictly at the experienced developer looking for a reference work. That makes this incredibly useful. These days I carry this book (thankfully light despite being 700 pages) between sites all the time. The lovely posters from Lotus might list all the properties and methods, but these guys provide the details underneath it.

The remarks on each class are pertinent, yet brief (as for NotesRichTextItem, "you must call the save method of the parent Notes document to save the data to disk") They include examples not only for classes, but also occasionally for methods and properties.

Interestingly, a quick check of the index for 'Index, databases' found only a reference to the updateFTIndex method for Java Database class and not to the LotusScript NotesDatabase class, while 'Registering Users' listed the LotusScript page and not the Java one. Perhaps the editors need to work on that. Fortunately, they provide a lot of cross-references on the pages, giving you page numbers for the classes mentioned in the text, reducing the need to refer to the table of contents or the index.

The print's small, but they use fonts, abbreviations and familiar symbols to get the message across clearly.

On balance, it's well worth the (money) I paid Amazon for it - it probably saved me an hour today and none of our hours come cheap, do they?

I bought this book originally expecting a full reference to Lotus and at first was a little dissappointed that it only covered LotusScript and Java. After reading it, now it is the only reference I use for LotusScript. I too have several other books, but none give the information and detaill in an easy to read format like this book. Anything you want to know about Classes, Methods, Properties, Events, and new R5 LotusScript features are covered in this book in detail with good examples. I also like how each class has it's own contents page giving page numbers for all of the assosiated Properties, Methods, and Events for QUICK reference.

This book has minimized my LotusScript related headaches! It is a one-stop resource for methods and properties for the predefined LotusScript Classes. It is hard to believe, but ()it takes me less time to write scripts, which gives me more time to enjoy the finer things in life. I would highly recommend this book to anyone, beginner or advanced.

The authors did a great job providing examples of how the properties and methods are used. I haven't written any Java yet, but when I do this book will be right by my side!

If you are new to LotusScript do not buy this book. This is a reference book for LotusScript and Java classes and a very good one at that. The developer help files can be confusing at times and it always helps to have a reference book near you.

If you are an intermediate or experienced Notes developer this is a terrific book, I have it by my desk all the time.

If you want a book to teach you LotusScript but Practical LotusScript it's great!

Exactly what I've been looking for: A no nonsense reference manual for the LotusScript and Java class libraries. Probably the most useful book a professional Notes/Domino developer can have.

This book is clear, concise, interesting (almost like an unputdownable novel by Sidney Sheldon). I'm not joking. You can read it in one or two days, do the transcenders, print out your transcender results. Before the exam review the transcenders and walk out with a 900 like me. I must mention i have six months admin and six months support experience. Just to let you know the experience level. Good luck to all.

This book is clear, concise, interesting (almost like an unputdownable novel by Sidney Sheldon). I'm not joking. You can read it in one or two days, do the transcenders, print out your transcender results. Before the exam review the transcenders and walk out with a 900 like me. I must mention i have six months admin and six months support experience. Just to let you know the experience level. Good luck to all.

Exam 70-073 is now the 1 exam most people take in order to become MCP and this book will make a big difference in the attempt. This book covers each exam objective and gives the detailed information you need in order to pass the exam on the first try.

The book of over 600 pages gives you exam tips, study tips, hands-on exercise, case studies summaries and review questions, exam questions and practice tests all to help you obtain your certification ....................

The book sis loaded with diagrams, pictures, tables and figures to make the learning process easier. The author takes out the mystery behind the NT Workstation and uncomplicates the technical jargon thus enabling to retain more information, and remember information is the key to passing the exam.

The book includes Top Score Software exam simulation; this allows you to try the exam before you go live. Overall the book is one for the technical library even after passing the exam.

As good as it gets - do not look farther....

I have looked at few of the books on this subject - this one is make you understand the subject in plain English - you do not feel stupid reading it.

Combine with a good exam test questionary - and you will make it...

I have right know - 5 books on this subject and I just passed the test on the first try with a 866 when only a 700 is required. I believe this book is what put me over the top and gave me some error room to boot! It is very easy to read and reminded me a lot of a textbook but thats a good thing, those "other" books try to make things much harder than they have to be. This book lays it out in a GREAT format. I found no errors unlike many other books and I recommend this with 5 star! - something I rarely ever give out. Good job to the author, keep it up! Highly recommend!

I had always had problems with trying to figure out how to use Sub Selects. Now I feel silly for not "getting it" quicker. This book has been a big help in me learning about the capabilities of MySQL in general.

Money very well spent.

This is also a great book for those just wanting to learn SQL. The examples are great.

If MySQL will suite your needs then this book is for you. I read the book cover-to-cover in my downtime at work over a few days and walked away with a solid understanding of MySQL.
Unfortunately MySQL isn't the most mature database solution, but if it's good enough for your project, then this is a great resource.

If you are considering MySQL you may not know how, but you are not a dummy. This book is not for dummys in that it doesn't patronize nor take you into convoluted scenarios, this book is for the reasonably intelligent who want to do stuff. What a blessing.

I was familiar with databases having worked with MS Access, but I had never worked with SQL. This book hit the spot in showing me what I needed to know to get going. I am now using MySQL successfully with a Java/Struts front end. While I found a few small gaps in this book, it has helped tremendously in my learning journey in that it gets to the point with minimum emotional overhead and verbosity, unlike MySQL (4th Edition) (Developer's Library) which I have found to be pretty useless and weighty after reading Forta's book.

This book has clear, short, well labeled chapters to find what you need. Highly recommended.

As others have said, this is a great book for beginners, whether in MySQL or in databases in general. Because I have a lot of database experience, I went throught it very quickly.

When I started to apply some of the techniques I learned to existing applications, I found out VERY quickly that this is insufficient as a reference. Each topic has enough hands-on examples to give you a start, but not nearly enough depth to use for looking things up.

I thought that Appendix B on creating the sample tables might have been a little abbreviated for the novice user. It refers to Chapter 2 to create a new datasource, but I think it was a little confusing jumping back and forth between the appendix and the chapter. This might be better as an exercise right in the chapter.

Overall, I would recommend this book as a starting point.

If you are fairly familiar with the concept of a database, this book could very well be all you need to get going. My issue with it is that it skimps on some of the very basic stuff. For example, it never goes over the syntax of the create call for creating a database, doesn't explain calling mysql at the command prompt as a particular user, gives you 11 chapters on manipulating data before showing you how to create a table, waits for chapter 28 to mention administering users, and puts datatypes in the appendix. These are the first things I wanted to learn. By the time I was done googling these concepts, I got pretty good at mySql and knew where to find better resources. At that point, the book became a very light reference.

A very usefull book, well written and with a deep analysis of the entire subject. I learnt more from this book then any other.

I felt there could have been much more tips and tricks on restoration of old photographs.

This is easily one of the best Photoshop retouching manuals ever. As a working photographer who enjoys doing his own retouching, I am always on the look-out for any instruction or manual that will make my job easier and workflow smoother. This book has migrated from my Photoshop bookshelf to join only four other books right alongside my monitor on my desk. When I need to address some specific problem that needs to be retouched, this is the first book I reach for.
The author has laid out the chapters in such a logical way, one only needs to look up the issue and go to the section that addresses the specific topic, a huge time-saver. As with Photoshop, there are many ways to correct images and this book presents quite a few new ones, even on techniques I use every day. I especially enjoy the before/after images and I'm sure many will benefit from the step-by-step lessons the author presents in a friendly, conversational way. Also, the "Tip" and "Caution" highlights are very helpful and concise.
I would highly recommend this book to anyone who wants to work in PS3 efficiently and profitably. Truly a Photoshop Retouching Bible in every way!

This book is more than just a restoration and retouching. Mark Fitzgerald has included the basics of photoshop in a clear and easy to understand way. The book is easy to navigate and find answers to your questions. One of his suggestions saved me hours of work. I highly recommend this book, it is a must have in anyone's photoshop library!

Having read most of the various Adobe Photoshop Help books, this book Photoshop CS3 Restoration and Retouching by Mark Fitzgerald is hands down the most organized and helpful of them all. His information is never too verbose which is a plus in a world of complex computer jargon.
Anyone, who has read books on this subject will be pleasantly surprised by the wealth of information (and how to use it) that the author has put forth.
Stephen Anderson

I love this book. It makes my life easier. What more could you ask for. This was just what i needed.

In one word WOW! You have to have this book, Matt explains things in simple terms and makes using PSE easy to use.

Bill

MATT KLOSKOWSKI DOES AND EXCELLENT JOB. VERY EASY TO FOLLOW! MATT'S HUMOR IS A DELIGHT. THE EXAMPLES MAKE IT EASY TO LEARN.

THE ONLY NEGATIVE IS THE BINDING ON THE BOOK. IT IS OK SO FAR. BUT I USE A BOOK HARD, I AM CAREFUL. BUT MYEXPERIENCE WITH THIS TYPE OF BINDING IS NOT GOOD. THEY SHOULD USE A SPIRAL BINDING.

This is a wonderful book. I have had it now for almost a year and use it constantly. It reads like a recipe book, which makes it extremely user friendly. I use it alone and in conjunction with "Photoshop Elements: The Missing Manual".

I echo the comments from everyone else. This is the best choise book to buy to learn how to use this product.

If you want to understand and write professional Windows Service programs, buy this book. You will find good C++ examples and best practices in Windows Service writing.

There has been so much written on the reviews for this book that I don't think I want to repeat all the good stuff said about it. The author has presented the various topics clearly and I like the style of writing. This book has been a great help. If you need to understand NT Services and how to program something decent; this is the book. Not for someone new to Windows programming. Just hope he comes out with another book soon.

The book is comprehensive, clear, and easy to read. The source code works and it is easy to follow (the code is available on-line.) The discussion on ATL COM servers is truly enlightening and by itself worth the price of the book. If you are writing an ATL COM server this book is a must, especially if it will be a multi-threaded server.

From the beginning the author has the attitude that NT services are easy to understand and his "prophecy" becomes self-fulfilling throughout the book. The book is well organized and it pays special attention to service design and usage patterns.

Also notice that the book does not cover hardware drivers. By the way, do read the previous review titled "One of a kind" as it gives very useful tips on installing ATL services (using "myservice.exe -Service") and housing COM objects in a service; I have not found that information in the book.

This book addresses all the issues related to such complex problems as NT Services. The author explains them in very great details, and makes you understand how all this works. The sample code works and you can use the classes from the book to start coding NT Services very fast. The author is very talented in explaining difficult concepts. Funny enough, this book has the best explanation on MSMQ, as well as apartments. As an alternative to the classes provided in this book, I recommend the CodeGuru NT Service C++ wizard written by Joerg Koenig. But even with a wizard, it is good to know how all this works.

No other source compares to the quality and convenience of Professional NT Services, either in book form or on the Internet. The only other way to get this information is to read sample code on MSDN, which is a less-than-optimal way to learn the subject.

Professional NT Services describes the issues involved in writing services, such as security and threading, and provides sample code every step of the way. The book also details how to build a service with ATL and even tells you how to improve ATL's implementation. It even talks a bit about Microsoft Transaction Server (now part of COM+).

Here are three bits of information that I discovered elsewhere that I wish were more evident in the book -

1. If you create an ATL service, the default registation code registers the EXE as a COM server instead of a service -- run "myservice.exe -Service" to register the service.

2. The easiest way for multiple clients to be able to use a single COM instance that's housed in the service is to implement the COM class using DECLARE_CLASSFACTORY_SINGLETON. This is your typical "server" pattern.

3. Clients that want to connect to COM objects housed in the ervice should use CLSCTX_SERVER in CoCreateInstance

Perhaps this information is buried in the book somewhere, but I didn't find it. At any rate, without this book, I wouldn't have known where to start.

Finally, for all its great qualities, the book needs to be revised for Windows 2000. It mentions some new features of "NT5" but I wonder how accurate this information really is.

Programming Language Pragmatics 2nd Edition (PLP2e) is a fantastic book that covers a great deal of information. It starts with explaining lexing and parsing, and then goes into scope, target machine instructions, control flow, data structures, a number of paradigms, and building a runnable program. It touches on pretty much every aspect of computer programming, and with deep and insightful knowledge.

While it's not as specific as some other books (language specific references, compiler construction texts, etc), it is a great beginning and reference for a wide range of topics. The bibliography of this book is incredible. I have marked a large number of papers/books from the bib that I now want to read in full.

The bonus information on the CD is also very good, including all the source code from the book, extra sections, and links to other resources.

This is among my favorite computer science books. I read the first edition straight through from cover to cover, even though I had some prior knowledge of the subject. I have since purchased the second edition, which exceeds the high standards set by the first edition. Scott's book would have made the programming languages course I took as an undergraduate much more enlightening, had it existed at the time.

As a software engineer, I tend to be picky about my books, but this one is very in depth and a good read. You will learn a lot about different programming languages, and why certain languages are better than others for solving different types of prroblems.

Every good programmer should know more than one programming language, that much is almost a consensus. But more than that, every programmer should educate himself about programming languages in general, what they mean and how they work. It's important to know at least the major programming paradigms, because they form the "mental model" of computation that is available to a programmer in a language from that paradigm.

And then it's always illustrative to know about the differences in many common languages, to see where different decisions have been made and what are the consequences. To know that certain legacy languages (e.g. C, Fortran) have features that were not designed because they were the "best" option (for some definition of best), but because the design was constrained by what technology was currently available.

This knowledge is not only required of compiler writers. It should be required of every good programmer. Compiler writers, of course, must know this, and probably in more detail. But Scott's book is a good resource about programming languages, in a level of detail that I believe adequate for all programmers.

There are two main kinds of books on programming languages: they are "survey" and "implementation".

Survey books show how things work in a lot of languages, comparing them along the way. Often the comparison gets down to small details that can affect the meaning, or semantics, of similar programs written in these languages. These books contain one individual chapter for every major topic, and inside such a chapter all languages are compared in relation to the topic. For example, one such chapter covers "subroutines" and then compare a host of different languages on how they implement subroutines.

Implementation books are different: they show how to implement many language features, usually by presenting code for interpreters and compilers. The reader doesn't learn that Ada permits nested subroutines, but instead how nested subroutines really work and how to implement them in a language, for example. A very good book of this kind is "Essentials of Programming Languages" by Friedman, Wand & Haynes.

I normally prefer the implementation books. I'm not really interested if Standard Pascal permits functions to be passed as parameters or not; if I do need to write a Standard Pascal compiler I'll look for a reference manual. I much prefer to know how to implement functions as parameters, and be done with it. Comparing minutiae about extant programming languages can sometimes be very enlightening, and sometimes be mostly dull.

Scott's book, however, really shines because it mixes feature descriptions and implementation details in the presentation. It does the usual routine of comparing a lot of different languages, most of the time the more popular ones like C++ and Java, but it then shows how the implementations differ because of differences in features. The book strikes a good balance between "language design" and "implementation" approaches, although it is clearly slanted towards design, and so more of a traditional "survey" book.

It wins over other survey books by including implementation information about almost every topic, and by the clear writing and style. Also, most survey books concentrate on mainstream imperative languages (nowadays C++, Java, C#) and leave other paradigms to chapters at the end. Scott's book is a bit better in this respect: the presentation often includes Common Lisp, Scheme and Standard ML in the comparisons. There are separate chapters about functional and logic programming too, but considerations about functional programming are spread in the whole book. This is important because paradigms change, and a good programmer must be able to adapt.

It's a good reference for language implementors and good education for most programmers. I look forward to the next editions.

Overall, "Programming Language Pragmatics" (PLP) is a very good book. According to the Preface:

"It aims, quite simply, to be the most comprehensive and accurate languages text available, in a style that is engaging and accessible to the typical undergraduate....

At its core, PLP is a book about how programming languages work. Rather than enumerate the details of many different languages, it focuses on concepts that underlie all the languages the student is likely to encounter, illustrating those concepts with a variety of concrete examples, and exploring the tradeoffs that explain why different languages were designed in different ways."

I'm not knowledgeable enough to pass judgment on "the most comprehensive and accurate" part. But, I'm pretty happy about the book meeting the rest of those goals. I read through the book on my own and have only a few significant gripes:

- Chapters 2 (Programming Language Syntax) and 4 (Semantic Analysis) are tough to get through. They're basically trying to teach enough about Alphabets, Languages, Regular Expressions, Context-Free Grammars, Finite Automata and Push-Down Automata for the reader to understand what the rest of the book is based on. I've read Cohen's Introduction to Computer Theory, which is dedicated solely to this material and I still had some trouble. With an instructor in a class to walk through the things, it should be doable. But, for a person reading the book on his own, ugh.

- All of Section III: Alternative Programming Models, seems to depart from the format of the rest of the book (as noted in the Preface) where the author talks about the concepts and then how the different languages implement them. Instead, he focuses on the languages themselves and almost seems to be trying to cram a primer into his text. Since the section seems to be a special case, it wouldn't be so bad except that the languages covered are a bit out of the mainstream and so that degree of depth gets pretty unreadable at times. Again, with a professor around, things would be better.

- At a more pedagogical level, the author has a tendency to merely explain what his example Figures are doing in general terms. The problem is that a lot of the code/pseudocode involves fairly advanced structures in several languages (many of which most people won't have run across). It would have made things a lot easier if he had walked his way through each of those Figures line-by-line and explained what each line did. Once again, this wouldn't be that much of a problem in a normal teaching environment since a professor could do it.

Other than those three things, this is a very good and readable book. I rate it at four stars out of five.