Software Books

Well laid out manual for learning some of the finer secrets of using Word 2003.

This book tells you exactly what you need to know for the exam. I was able to concentrate on the proper information without worry. I passed the exam first time :D

This book is for everyone, novice, intermediate and experts (who need a refreshers course). Its plain and to the point. There was one section of it that was not quite right, however, this is no fault of the seller but the writers of the book. Once you over look that it works just as stated in the book. The book got to my freight forwarder quicker than I expected.

Fast shipping. Book received in same great condition as described on website. All in all, an A+ transaction.

I've been using Word 2000 for years. I was finally able to get most of thr functions I needed to work, but it was a "try & try again" approach. The on line manual is helpful, IF you know what questions to ask. And most software has features you might not be aware of, and therefore can't use.

The Word 2003 Step by Step manual is wonderful. You can find what you want to do easily in the index, then get step by step instructions on how to do the project. You can just read the index and/or manual, and learn of the many features available that you never knew existed, and so hadn't tried to use.

It's like having an instructor on hand, any time you want one. I expanded my use of Word greatly, just by learning about new features, on learning how to do things I knew existed, but couldn't figure out how to access.

I highly recommend this book.

This book does a good job of doing exactly what the title says it would do. I bought this because at work our company has always lived in a Wintel World. But we acquired another company that was Linux centric and it was clear that us Windows people needed a crash course of Linux. I needed some quick exposure to Linux and a way to cut my learning curve by being able to understand how to transfer tasks in Windows over to Linux. This book shortened my learning curve because as good as the net is about giving information to us for free. Sometimes I just like curling up with a good book.

Firstly i live in a caribbean country ..there are no linux user groups ...any info yu get from linux if you find one, user you most likely have to pay for ..I successfully installed linux already but i had no clue what was going on after that ..i have reached chapter 3 in this book and if there were no more pages i already got my monies worth.This book is truly built with the linux dummy in mind ..thanks mr easttom

I hated Linux until i read this book. I haven't turned on my Windows box all month. Very clearly written and easy to read.

It is a book, explaining Linux in a simple,
clear manner. Best for a reader with some
Windows skills.

It was my old dream to learn Linux. I had heard that it
is a stable, free operation system. Having little
understanding about Linux before, I read the book,
installed Linux and now feel comfortable with it.

I found this particular book to be remarkably easy to follow, accurate, informative, and generally a great help. I am not a computer professional by trade, and my only experience has been with Windows. But like many people I have been quite frustrated with Windows and wished to try Linux. With this book I was able to install Linux and to use it to do all the things I had previously done with Windows.

I first bought this book a year ago, and have used what I learned to optimize computers that I would have normaly considered obsolete. It's allowed me to put off having to upgrade untill the new memory standard (DDR) comes out in march, saving me lots of $. I also bought copies for friends this year (2000) for X-mas. Some may say it needs updating, but the authors web site has all the info you would need updated. Many thanks for the Book Dave!

.............Curtis

I use computer frequently, but I am not that of an advanced user. This book really brings me into a higher level of understanding about how Windows works. The author goes into lots of detail about what happens while Windows is running (e.g. during boot up). Yet, the text is very easy to be understood. This book also gives me a new way to look at computing. A faster CPU doesn't always give you a faster computer. If you think your computer is too slow, THERE ARE things you can do to make it runs faster. When performance matters, you have to give up things that you are used to, but not usful. (I can't complain that my computer is too slow when I am using a fansy theme that costs too much memory.) Also, this book does not simply tell you what to do. The author's explaination enables me to make decisions on my own.

This is not a book that simply tell you how to improve your computer's performance. If you have some experiences in using Windows and want to know more about the operating system, this is a nice size book that can get you started. What's more? My machine is faster now. :)

This book has a huge collection of excellent tips for getting the most out of Windows. Every Windows owner owes it to themselves to go out and get this book!

I am an experienced windows user, and I bought this book because I figured it was cheaper than upgrading my PC. I run a K6 266 overclocked to 300, 160 megs of ram, 7200 RPM 27 Gig HD. Once I implemented ALL of the tricks in this book (This is no easy task... it takes a lot of time, and is very high maintenance), my system out performed my ex-girlfriend's Pentium III 850 with 128 megs of ram for applications (not for games, though it still does those well).

I don't mind making the effort, but some people might. If you have lots of time, and you love customizing your PC, you can't go wrong.

Litestep, registry hacks, DOS utils, 5 partitions on a HD... if you like this kind of stuff, get the book! If you don't know what any of these things are, you may be better off upgrading you PC.

This book is an attempt to collect (and organize) a series of tricks to speed up Win9x machines (it does work for Windows 95, 98 and ME, but most of the advices do not translate to WinNt and Win2000, as the author honestly points out).

The author's idea is that you can actually obtain a lot of performance even from older machines, if you are ready to do some work for it (tracking down utilities, testing different configurations, dropping some "cool effects" in the standard UI and so on).

I've recently applied the book ideas to "renew" a couple of very old machines (a 486-based, 24MB ram Compaq portable and a Pentium-75 with 64 MB Ram). I am not a Windows Guru by any stretch of the term, and I did learn a lot on how Windows is organized in the process. This fact alone is probably worth one extra star in my rating.

The book is clear, and is a good read (i.e. it is not a simple itemized lists of tricks, but tries to tie up things in a coherent thread).

Unfortunately, the end result of my attempts to optimize my two museum-quality machines were less stellar than what other reviewers submitted. I think that the main reason is due to the fact that most of the tips seem to be aimed at computers which have been subjected to a lot of "install-the-new-software-gizmo-I-just-found-in-this-magazine-CD".

If you start from a clean installation (or work on a machine on which little extra sw was installed) there seems to be very little gain from applying most of the techniques offered by the author.

Another problem is that both SW and HW are a moving target, so when you try to obtain some of the utilities which the author recommends, for example, you may find out that the current versions may have grown new requirements which makes installing them on an older machine a little troublesome.

This is even more obvious when we talk about RAM or other HW specific issues.

All in all, I'm pleased with the book, but mostly because helped me to better understand how Windows works. People who already have a lot of first-hand experience in installing and maintaining Windows machines would probably give this book three stars at most.

This is the best "How to" book on Oracle. I have read around 20 books on Oracle (I reviewed most of them on Amazon) and this one is the most practical Oracle book for intermediate to advance Oracle DBAs.

The book skips most of the architecture and goes directly on how to configure and use some of the most salient features of Oracle 10g.

Some of the examples are:

1)How to manually install RAC instance
2)How to migrate Non-ASM to ASM disks and vice versa.
3)How to collect AWR reports using builtin scripts.
4)How to install CRS
5)How to Flashback Database and Flashback Table.
6)How to Patch Dataguard Instances
7)How to use flashback in Dataguard Standby.
8)How to manually remove Oracle Instances.
9)How to upgrade RMAN Catalog.
10)How to use Wait statistics to measure and improve performance.

Not all the topics are advanced. But it still helps to get down to the fundamentals, even for the advanced DBA with decade or more of experience.

I highly recommend this book for anyone who wants to expand/improve their Oracle 10G skillset.

This is a really good book to have by an Oracle DBA for Oracle 10g reference. This book will help the Oracle DBA to identify and implement Oracle 10g new features. It has good tips for performance and tuning and setting up ASM. I give this book 5 star rating.

Highly recommended reference book for DBA's that are familiar with previous version of Oracle and wants to find out the new features of 10g.

This book covers Release 2 of Oracle 10G. Concepts are presented in a clear manner. Each chapter can read in an hour or so. This is a great place to start for new DBAs. For experience DBAs, this a great book to get to know the New Features. Book is very easily read. Best book to learn Oracle 10g R2.

This book is easy to follow and drives straight into chapters essential for 10g. It does a wonderful job and covers installations on various platforms, new features and approach for identifying the performance issues. It provides practical advice using practical approach, tips and examples. I highly recommend this book to anyone who is learning or working with 10g.

A great read. Much more practical and easier reading than some of the classics in the code inspection theme.

Practical is a key element of this book. Like Wiegers' other books, this one is well written and researched; it provides a concise guide to peer reviews along with a set of useful tools for the practitioner, or "assets" -- documents, procedures, and spreadsheets that you can implement right away to put reviews into practice.

It's amazing, but peer reviews are not a regular practice in many software organizations. Peer reviews are proven to save time, money and promote learning and understanding among project team members. Perhaps one reason for their lack of practice is that there has been, up until now, little in the literature that we can read and put into practice right away. Well, here it is!

One of the nice things about this book is that the author shows you how you can tweak peer reviews to make them work for your team or organization. He give due diligence, the psychological aspects of peer reviews. Wiegers explains all the roles involved, target work products to review, how to prepare for a review, what to record, what to measure, and even how to train on peer reviews.

The book includes a useful glossary, a set of troubleshooting review problems with symptoms and possible solutions, and those very useful assets on the author's web site(...). Example assets include: peer review process description, inspection checklist, spreadsheets for code and document inspection and a set of defect checklists.

Used in the context of careful reading of this book, teams can really do a lot to improve their products and relationships. This is a book to be read by analysts, developers, architects, project leaders and managers who care about the quality and cost of software.

I have attempted over the years to get various organizations to buy into peer reviews. We have lots of evidence why these reviews are highly worthwhile, but their implementation has not been anything to write home about. There's always many reasons why organizations don't buy in or give peer reviews half-hearted support.

In my opinion, this book is an important contribution to the field. I'm sufficiently impressed that I've passed copies of the book to a few busy software development managers, software engineers and business managers so far. They've taken the time to look at it, and they find the book talks to them -- it is clear, addresses their issues, offers practical solutions which they may not have considered before, and is persuasive. I believe the book will have a postive influence in their organizations.

I hope to see copies in lots more people's bookshelves.

Excellent up to date survey of the literature, excellent survey of the many methods and analysis of their differences. A rich insight into the area of peer reviews in general, including Inspections and their variations. Practical for the industrial user. Highly recommended.

Every developer I have known has experienced the phenomena of spending an inordinate amount of time searching for a bug only to have a colleague look at the code and find it almost immediately. Study after study has indicated that the worst review process for software is self-criticism and the best is to have other coders take a good look at it. Therefore, it is logical that a formal process for developers reviewing each others code be implemented. The problem is that the former is informal, making it "off the books" and not subject to review by decision makers. Being human, developers react differently when their livelihood is potentially at stake, which can cause problems and prevent adequate reviews of the code.
Creating a stable, scalable and structured peer review system is not something that can be done by fiat or in a short time. It requires clear managerial direction that inspires confidence and builds a sense of security for both the evaluator and evaluated. Creating such an environment is the key and that is the main point of value in this book.
Wiegers lays out in great detail how to create a culture where all involved are peers in the real sense. It is absolutely necessary that everyone in the review process understand that creating quality software is the only thing that matters. Therefore, posturing, ego tripping, ego inflating, ego protection and all related activities must be suppressed. These are the most difficult tasks for professional humans to engage in, and it requires a combination of carrying a big stick to move the process as well as a soft pillow for the necessary falls from perfection. Wiegers shows you how to do this with the skill of a counselor.
In my reading of the trade press, the recent rise in the concern for computer security has led to a great deal of coverage about errors in software. Responding to this pressure, Bill Gates has sent out a public memo noting that quality is now the number one priority at Microsoft. The best way to achieve this quality is to have an effective peer review process and in this book you can learn how to do that. In the new world order of software, your very survival may be at stake, so your plan of action should include a rendezvous with this book.

This is one of the best "how-to" books on computer imaging that I ever read. Each example is complete in itself -- they can really hold my interet throughout. The steps cross-reference accompanying pictures precisely. Everything is Thoroughly and methodically laid out -- no missing pieces or glibbed over details to stump readers.

This book really allowed me to learn masking in Photoshop. The step-by-step instructions allow you to follow the descriptions on your computer and see the results. It is rare to find a great book in Photoshop that teaches you so much. I would recommend this book to anyone who seeks to understand how to do collages using the mask technology in Photoshop. You won't regret buying this book at all. I can only wish there is the same kind of book in Illustrator and Painter and all the other graphics programs I use so that I can have a better understanding of the full special functions that are embedded in each of those applications.

Greg Haun is a master of Photoshop special effects techniques.
I was fortunate enough to take several of his classes at the Pacific Northwest College of Art here in Portland
back in '94 and '95 when 3.0 Photoshop was just out!
Greg always showed personal interest in what you were doing.
Greg is a professional among professionals, yet you would never know his level of expertise unless you asked him point blank! He was a very humble guy and believed you could learn techniques from even a novice.

Because of those early years of study, I recently achieved my expert certification in Photoshop. I doubt that I could have done it had I not had the advantage of Greg's tutelage.
He made a difference in my life. I can't thank him enough...

This book is a must for the professional Photoshop user.

I was fortunate to take several classes from Greg during the early 90s when he still taught at the Pacific NW College of Art. He was very patient, very knowledgeable and a great guy. He always made time for you and always had an answer. This book is invaluable for Photoshop students of all levels! Buy it!

Mark Simon, Graphic Artist - Dex Media Yellow Pages - Portland, Or

As a certificate program graphic design student, I found this to be one of the best books on Photoshop, even though it was written prior to the new software versions. It is well-edited, and explains masking, layering, and blending images clearly and concisely with very helpful screenshots of what you need to do.

As all the collection of this books it is good to have this in your personal library to check out how filters work with different kind of pictures, of coarse these books are directed to professional photos, but you can maybe experiment with your personal as well, I just wanted to point that out because in the book the examples given are for applying filters to pictures you maybe wanna show or give to a client.

But as a reference book is just great, I mean someone took the time to write and visually show you all the filters in photoshop and as its name it is a real encyclopedia, where you can look every filter how is going to look like and then decide.

Buy this it will always be useful

Of all the things that Photoshop can do, the Filters option certainly is one of the coolest options available to users. Taking a digital picture or just a standard graphics file, you can use the power of Photoshop Filters to create unique art for whatever purpose you want. From a colored pencil effect to blurring images to one of the newest filters "Vanishing Point", this book is an absolute gem.

If you use Filters on a daily basis and want to see what can be done to take a normal image and make it stand out from the "blah" that is out there in the world, this book is for you. If you are a heavy Photoshop user but want to go beyond the basics of just resizing images and cropping pictures, you will also heavily enjoy this book. Of the 4 books in this Photoshop line I love each one of them and feel that all readers should rush out and pick them all up for their reference.

The only downside of this book really isn't a fair one at all, and that's that I wish there were more pages and examples dedicated to all of the filters covered here. Obviously this isn't a realistic gripe so it's barely even worth mentioning.

***** HIGHLY RECOMMENDED

For anyone who uses Photoshop in graphic design and or to correct or edit their precious photos, this book is a must have in your library of reference materials. It takes the mystery out of all those scary, misused, underused and never used filters in Photoshop by clearly showing and explaining how to use them and when to use them. This is one fantastic book.

The O'Reilly Studio put their thinking caps on for all ages and levels of expertise at Photoshop. The step by step instructions with options made this, as well as all their other Cookbooks, a delight to learn from and practice with, in an easy-to-understand format. I would love to see them come out with CD's for their books included.

To be frank, I bought this book because to get free shipping, I had to add one more book to my order of "Photoshop Cosmetic Surgery, by Barry Huggins. It was one of many that I could have chosen for this purpose, but I chose it because it appeared that it could illuminate in detail an area of Photoshop that I was interested in exploring in greater depth than I had previously been able to do. In general, I am satisfied with my choice, although there were some areas where I would have liked greater detail and explanation. This book is not for a newbie to Photoshop. It assumes a reasonable degree of familiarity with the program, and simply proceeds, without fanfare, to describe how to use the many filters and their settings. I recommend this book for a reasonably competent Photoshop user who wants to continue to increase his/her mastery over this wonderful and hugely flexible program.

A must-have for anybody working 6.5, 7, and 2000 MSSQL. Very well scoped-out in its depth of coverage. Explains aspects of the RDBMS that will be required knowledge for any DBA coming from a non-MSSQL background. Covers differences from SQL 6.5 through SQL 2000. Sure, there is a lot that is not in here, but it is impressive how much is covered (from basics of physical design, to ACID transactions, to replication-related stored procedures). The smaller form factor makes it easy to carry around, which is an absolute bonus. The material in this book (and the "for Experienced DBAs" book in the Osborne series) must be distilled from a vast amount of real-world experience-- sadly, not out there yet for SQL 2005.

This is an essential book for anyone who works with, or is curious about SQL. This book covers all aspects of SQL from installation to Back Up and restoration scenarios. Covering all flavors of SQL from version 6.5 to current this book is compact and contains an unbelievable amount of knowledge into less than 500 Pages. I could not get over how detailed and clear this book is. After having read many other books on these topics it was truly refreshing to read a technical book that succinctly touched on all aspects of administrating a SQL box.

It was unfortunate to discover that some of what I had thought was good techniques were proved to be flawed, and when after implementing the suggestions in this book I was thrilled to see an increase in efficiency of Data Calls, and Network Load.

It is clear to see that the authors of this book have carefully and clearly defined all that could be needed in a small easy to reference book. This book is a necessity for any desk where SQL Server is running. It is a small cost to pay for so much knowledge, well worth every cent.

If there is one book that you are considering for SQL Server Administration, this is the one to buy. Covering all the major topics of administration, this book goes above and beyond other SQL Server books for several reasons. Not only does it live up to the promise of an easy to find guide for everyday tasks, it offers the ability to read up quickly on several advanced topics and gain knowledge rapidly. Taken into consideration, are the three latest versions; SQL Server 2000, 7.0 and 6.5, detailing out differences between versions where applicable. Everything is explained clearly. The authors have done an excellent job of providing a wealth of information in short and concise content. It is very refreshing to see a book that was obviously written to be as brief possible without skimping on important details...clearly no fluff here!!!! This has two benefits to the reader, 1; information is easy to find, no time is wasted reading through frivolous content, 2; the cost is lower than those 1,000 page volumes that contain less valuable information. Hopefully this is the start of a new trend in technical books.

In just a few minutes after flipping through, and reading up on backups, I realized that I'm not backing up my production data properly, and can substantially decrease data loss risk by backing up my transaction logs regularly with the data. Also, some security concepts I had a bit of difficulty fully comprehending became clear to me as well.

Reading through this book, it is obvious the authors have extensive experience with SQL Server, as this book has many insider tips that only experts would know through practice. It is also apparent that the authors worked well together as this book reads as though one person wrote it. Definitely a must buy and well worth the cost. I wish I could give this book more than 5 stars.

This was a great read! Very concise and packed with useful information that no DBA should be without. Whether you are a SQL specialist already or new to SQL altogether, this book is packed with great information in one, small and manageable format and an easy read. Kudos to Steve and Damir!

Even though I have read only the first two chapters so far, I can still say this book is definately worth owning. The amount of information in the introductory chapters alone make this book a worthwhile purchase, especially given its relatively low price. The author's writing style is conversational without being condescending or idiotically simplistic. Reading the book, I feel I have an experienced friend giving me many worthwhile tips and suggestions. I really think you will find this book to be a worthwhile purchase.

Although this book is over 10 years old, it could have been written this year. The concepts are still relevant.
The author concludes that there are 2 primary reasons to undertake a metrics program for software development -- 1) tracking progress and 2) identifying improvements. The book is divided into 2 parts, with the first part discussing project management metrics and the second part metrics to improve your software development processes. I particularly liked the goal/question/metric approach to validate the metrics you are collecting. The text is loaded with examples from the author's experience at HP. There are several charts and diagrams. This is not an academic read, but as the title says -- practical. The author also covers people issues, such as selling your metrics program to management and staff. It is a quick read and a very useful reference book.

This is Grady's first book and it sets the tone for his later two books, Successful Software Process Improvement and Software Metrics: Establishing a Company-wide Program. What makes this book so important is that it is one of the first to integrate software metrics with project management metrics.

What I particularly like about this book includes:

(1) Complete view of metrics that matter, and the chronicle of how these metrics evolved in a large company (Hewlett-Packard).
(2) Recognition that any software metrics initiative extends beyond the project that delivers the software - Grady examines post-production metrics and ties them back to not only the development life cycle, but the product life cycle as well. Ten years after this book was published there are still large organizations that are struggling with doing this, yet Grady's book provides a clear roadmap to achieving this elusive goal.
(3) Continuous improvement is the central theme in this book. Grady does not stop with collecting and analyzing metrics, but how to effectively employ them to spot improvement opportunities and develop a strategy to effect those improvements.

The book is written as both a story of how a successful metrics program evolved, complete with anecdotes that will prove helpful, and as a collection of data that illustrates what is and is not important to a comprehensive metrics program.

Among all of Grady's books I like this one the best; however, I recommend that his other two also be carefully read if software process improvement is your goal. He has much to say and backs it up with data and a chronicle of his experiences from real projects.

I bought this book about 5 years ago after getting certified as a project manager. This book give me a holistic view of how to intepret data collected from tracking the entire software lifecycle and manage and integrate best practices into a software business.

The author's vast experience in HP helps to provide good assurance that his concepts used were tried and robustly tested. Therefore, software failures, internal flags and customer feedbacks can immediately give you a fairly visible prognosis to the robustness of a release and flashes early warning signs of how you should manage that product to reduce damage to your business, etc.. Practical for technical managers having to manage the business operations.

Whether you're a fledgling company trying to design quality software with no guidelines to go by or a well-developed organization with processes in place, this book offers up many ways that you can improve your software quality.

I was introduced to Mr. Grady's work when I borrowed a copy of Software Metrics: Establishing a Company-Wide Program. Where that book interwove a storyline into metrics and how they support mature process improvement, this book is more like a desk reference. Mr. Grady has divided this book into two parts: tactical metrics, which are project-oriented, and strategic metrics which address process improvement.

The first part starts with a collection of practical rules of thumb for software managers. This collection of heuristics covers every phase of the development life cycle and are backed up with data gathered during 125 software projects at Hewlett-Packard. An example of one of these rules of thumb is that you will find 1 defect after software has been released into production for every 10 defects caught during testing. This, of course, is purely empirical, but is an interesting rule that I mentally filed away. Some highlights of the first part are: a good introduction to the goal-question-metric approach to determining what to measure based on your objectives, and a focus on project goals of maximizing customer satisfaction while minimizing project schedule and costs, and product defects. This is followed by chapters that address each of these goals. One of the best chapters in the first part of this book is work analysis. While I am more focused on the service delivery side of metrics (after the project has produced something that has been released into production), some of the metrics were very valuable to me - especially the ones that revolved around testing and QA.

Part 2 is squarely in my domain - production and application support, and service delivery. The best chapter, Dissecting Software Failures, was one of the most insightful descriptions of the defect life cycle I have ever read. It fully addresses defect data collection and analysis, and how to use this data to effect process and product improvement. Even better is the chapter on investing in process improvement. Here Mr. Grady gives a workable approach to using the defect data to developing a business case for process improvement. He guides you through developing a plan, selecting from among an array of solutions, and case studies.

This book is a quick read. It's main value lies in the many tables and facts provided on nearly every page. I use it as a desk reference, especially the appendices that summarize defect origins, types and modes, and metrics definitions. It spans both project and production metrics, and is as valuable to project managers as it is to application support professionals.

Pro Ajax and the .NET 2.0 Platform gets high marks from me because it is concise, informative and easy to follow. After reading the first three chapters I had a clear understanding of what Ajax really is. Author Dan Woolston has extensive experience with AJAX and he seemed to share it all here without overwhelming this reader.

Woolston did not waste my time in getting me up to speed. In the first three chapters I learned how to write my own reusable (cross browser) JavaScript functions that will work together to execute an Ajax call.

Of course I might rely on one of the various existing frameworks to do this for me. However, now I know what's going on under the covers and I can make an informed decision about what Ajax to use and when. I know exactly what is happening when Ajax is implemented and why.The book also does a nice job of covering CSS and the DOM (document object model). As you know (or will know after reading), these combine with JavaScript to create the foundation of Ajax! Once you understand how they work together you'll know more about Ajax than 90% of your developer friends.

Excellent Feature #1: The overview of JavaScript, CSS and the DOM is fantastic. I really appreciated the fact that it was concise and dead-on accurate in addressing the specific elements that a .NET developer needs to understand in order to code Ajax.

Continuing on, after the book had me up to speed with Ajax, it went into n-tier design. This is important because, in theory, a programmer can go hog wild on Ajax and break tons of rules regarding sound application architecture. So I was impressed that Woolston transitioned directly into best-practices for how and when to use Ajax.

The first third of the book covers Ajax theory and best-practices. With Ajax, one size does not fit all. Therefore, chapter seven includes overviews of many popular Ajax frameworks including non .NET frameworks such as Ruby on Rails, WebORB, xajax (PHP) and Direct Web Remoting (Java). It also covers .NET frameworks including Ajax.NET, Anthem and Atlas.

The other two thirds of the book are devoted to Ajax programming concepts. The author uses the Anthem framework for most of this coding. Anthem is an open-source, .NET framework in C# that is compatible with ASP.NET 1.1 and 2.0. It is extremely lightweight, requiring only one class file for core functionality.

Excellent Feature #2: The book's code walkthroughs are based on a fully functional n-tier sample application that you can download free. The sample application uses the AdventureWorks database which is also a free download from Microsoft if you don't already have access to it.

You might think that some .NET features and topics lend themselves to Ajax technology and therefore should be covered in more detail. You'd be right. Woolston sets aside complete chapters on Web services, Custom Controls, ASP.NET Security and Web Parts.

Excellent Feature #3: When you're done learning how to build your own Ajax, there are two chapters devoted to debugging and testing Ajax.

One of the last chapters was my favorite. Chapter 19 is all about usability. As you may know, Ajax solves many usability problems. But can also create new ones. Woolston addresses the good, the bad and the ugly.

The book provides ideas and examples of good Ajax. The author has test-driven many Ajax controls and shares his trials and tribulations. This feedback no doubt will save developers valuable time.

The book also discusses potential pitfalls of using Ajax. Woolston tackles cross-browser compatibility issues and how to best overcome them. He also talks about how to deal with the browser's back button. How to handle browsers with disabled JavaScript and how to work past the problem of pageshifting.

Some of the other usability topics covered in Chapter 19 include Ajax menus, bookmarking, type-aheads, connected controls, code visibility and page paradigms.

Suffices to say this book packs a big Ajax punch. I highly recommend it to any of my peers who are interested in building Ajax functionality into their web applications. This book is applicable to .NET developers who are working with ASP.NET 1.1 or 2.0. In my opinion, web developers of any skill level will find it helpful.

About 3/4 done with this book. Today I just built my 1st Ajax feature in a few hours at work with the suff I learned. This books is a quick read with great examples works in both 1.1 and 2.0. Buy it!

i didnot think that i would like this book because for me apress is famous with their books having lacking style of examples. Normally you find yourself lost in the examples eventough the topic is covered very well.
This book is different than others absolutely; it starts with what is ajax; and why ajax and with simple examples.
if you dont know javascript; it is still ok because one of the chapters covers javascript; so you can learn enough javascript to handle the simple ajax pages.
Before diving into ajax; it tells you about different ajax libraries; so i like this part too; you will have an idea about other ajax libraries too.
I could not run the first example which is the easiest one and i struggle a lot to solve it;but most of the codes in the book is easy to implement.
And guess what; as you can see from the title; the book is for .NET developers; so if you are a .NET developer; this is right book to buy.
It is not like other apress books that have coding examples problem. the sequence for the chapter makes the book easy to follow.
After reading this book; i start reading some tutorials about Atlas ( which is basically Microsoft's Ajax ) and it really helps you to understand atlas too;
If you like google maps; or virtual maps; this books has a suprise for you :)
i read 4-5 different books from apress and this one is the best; i will highly recommend this book to all .net developers who want to learn ajax with .net

I hardly ever review books and probably wouldn't have bothered this time if it were not for an email from Amazon seeking one. I decided to go ahead with a review because this book really filled a need I had for working with AJAX for the first time. It had me up and running in very short order. Did it go over a couple things along the way that I already knew? Yes. But I didn't mind it in that it treated all topics in an intelligent manner and helped explain where AJAX fit into the broader world of web development. Definitely geared for .NET. That's what I wanted. If that's what you're looking for, you won't be disappointed.

I had done some little test applications utilizing Ajax and/or Atlas prior to reading this book, and I wanted this book to really give a solid base from which to move forward with.

Mr. Woolston's writing style is personable but not too over the top. One thing I did not like about the writing style is the manner in which code is laid out at times. For instance, with many of the sample applications, Mr. Woolston will dump about 5-6 pages of code into the book and then work towards restating it in part afterwards with some explanation. I can see where it would be useful if not in front of the sample code/a PC, but in reality this book will not be useful if not in front of a computer working on the examples.

There are other times where some of the content is not really useful in furthering education about Ajax and certain examples it feels are stretched to make the chapters longer. I think there was likely a challenge in filling out a reasonable sized book because simply put - the fundamental elements of Ajax aren't that complex. I found myself done with the book in a period of less than a week.

Those things said, after reading the book I can certainly say the overall content has an excellent "perspective of the landscape". From a history of Ajax to a little primer on Javascript, CSS/DOM, and the XmlHttpRequest, he moves forward to examples of Ajax demonstrating the technology with an Ajax framework named Anthem. The main meat of the book are really these examples, where practice implements the ideas from the prior chapters.

Lastly, the book closes with a few chapters covering security, testing, usability, performance, and a token chapter on Atlas.

One other element that I appreciated in this book was the identification of a few free tools out there to aid in Ajax development. Those tools in their own right would have definitely contributed to some time savings a week or two ago when I was struggling with a couple DOM/CSS issues prior to reading this book!

In summary, perhaps a book stretched to fit it's cover but nevertheless a very useful read to me and I would certainly recommend it.