"A soldier is trained to fight the good fight...but it helps if he knows who the enemy is."
Blair writes science fiction and about the military as though he'd visited the planets he's writing about while a member of some mobile infantry. In short, though the premise may seem a little far fetched (it is sci-fi, after all), it is told with the exuberance and detail that makes you wonder if it's made up at all. The lead character, Clay, is a good example of the hero, or even anti-hero, in modern literature. If you are into sci-fi, if you liked Starship Troopers, Predator, or Alien, this book is for you. Enjoy.

ASP XML is simply not well written. I shall compare it to an EXCELLENT wrox book 'Beginning JavaScript' to explain myself.

Beginning JavaScript has a superb index, in 5-10 seconds, I have a reference to information I need at any time. ASP XML has virtually no index - it has been useful exactly 0 times. This means you have to read all 800+ pages to get good information.

ASP XML has a decent object reference, but no cross-reference to code (you have to scan the whole book to find applications), BJS has excellent code samples in the Core object technology appendix.

ASP XML has out-of-date and inaccurate information on XSL (more accuratly, it is missing info on XSLT), BJS describes differences between JavaScript versions much better.

ASP XML's chapter categories are rather convoluted, BJS's categories are very straightforward and follow the proper pattern for any description of a programming environment.

ASP XML is still a beginner/intermediate book, so it should have: Introduction, DOM, XPath, XSLT, XML and CSS, String Functions, Database Functions, and then the advanced topics. The book skipped details on XPath (trust me) and details on string functions, making my knowledge inadequate to understand the rest of it. Translation, the book felt incomplete.

It may be that all of what I needed to understand XML really is in the book, but I can't find it because it is so disorganized.

I know the authors are brilliant (Having seen some of their programs) but if I can't understand them, it doesn't matter.

Donald Derrick

The chapters are laid out properly and are easy to understand. It helped us to learn a great deal about incorporating XML into ASP.We recommend this book to anyone who wants to further expand their knowledge of XML in ASP.The authors did a really good job on explaing XML for ASP developers.The depth explainations of the case studies & examples and XML are really great and relate to real world examples.The chapter explaining about the SOAP is really good which helped us a lot personally to implement an in my current project . We personally thank Dinar Dalvi for his help and support to answer our questions and immediate feedback for our emails.

Excellent! for ones who are pro to ASP and need to intergrate XML with ASP! A must buy!

I was disappointed that a book this size had such limited descriptions of the animals. Nearly half of each page was devoted to a map which showed the areas where the animal might be found. The pictures of the animals are black and white sketchs with no color descriptions in the text. Can you imagine trying to identify birds without knowing what color they are? If the map had been scaled down there would be plenty of room to give more detailed descriptions of the creatures. The idea is very good, but the book is a disappointment.

With regard to the above comment, I'd just like to point out that this book is an atlas of Oregon wildlife, not an identification guide. If you've ever tried to scope out the range of a species from the tiny maps in most field guides, you'll appreciate the large size of these maps.

This book is not based on Visual Studio.Net Final Release!

I have read the book front to back including introduction page. I just realized that the book was based on beta 2 of Visual Studio.Net, too late for a refund. Anyway, I went on to read it and found out that the book was not very much organised as tons of '...we'll discuss this on chapter xx ... ' appear no less than 5 times in a single chapter (on some chapters). Mispelled words also are catching enough to say that this book was in a hurry to be printed.

If you're looking for a book that covers thorough details on window forms and web form control howtos, this wouldn't give you enough detail on those topics. Web Services is equally a mere introduction, with about two pages of discussion on UDDI as well as WSDL. Not much on ADO.Net and XML.

I should have borrowed this book instead and skim through it or should have bought it for 20 bucks less. Besides, it's already outdated. I hope the same authors would come up with a second edition that has richer detail...and send me a free copy.

I was planning on buying this book and noticed the out of print note on the Wrox site. Not exactly sure what out of print means.
Looks like other books based on the betas say out of print on the Wrox site.
If this book was released in August 2001 then it should have been based on the beta. They might plan on releasing an updated version.

I'd say this is the best Professional VB.NET book so far. I like the the ADO.NET part and VB control part of this book. Better than O'really ASP and VB book.

The book shown above is the hardcover edition. It's also published, without illustrations, in five paperback volumes. I read only THE TUDORS AND STUARTS, which had no illustrations other than two or three maps and graphs. The first half of the book, about the Tudors, was written by one man, and the second half, about the Stuarts, by another. The volume was short, only 142 pages.

This is my favorite period of British history and the one with which I am most familiar, but still, I found the text confusing. I think there were several misplaced lines of type in the second half. Maybe a writer can't do much in 70 pages to elucidate a period, and probably the illustrations would have distracted from the sketchy text. The writing was not lively.

The very last section is called "Intellectual and Religious Life," but it was mostly about religious life. Literature is almost totally ignored throughout the volume. Pepys is never mentioned.

There is no index. Perhaps the complete, one-volume version has an index, and the publisher didn't want to go to the trouble of compiling indexes for the individual volumes. Still, a history book without an index is unthinkable.

On the whole, the book was disappointing.

I'm a half-educated American, with the vaguest notions of British history. I bought this book hoping to be able to understand the story of the British Isles, in a more or less clear outline. That didn't happen: after 200 pages, I tossed the book, wondering just who it was written for. Here's why I tossed it:

(1) It doesn't have an author. Instead, it has a bunch of authors, each apparently assigned a certain portion of British history to cover. The problem is that none of the authors seem to have consulted each other, nor did the editor seem to edit. On every other page, you see a fact or definition repeated (by a previous author), or a topic referenced (but uncovered by a previous author). History is a messy thing, but it has to be organized to be learned, and any hope of presenting material in terms of themes or movements is lost, because styles and approaches switch radically from author to author, from clear and sparse, to confusing and overly-detailed.

(2) It should have an author. This sounds like point (1), but hear me out: the editor, Mr. Morgan, claims that writing grand history, spanning the length of the British past, just can't be written anymore. It is better, rather, to have specialists write about their specialities. Sounds good in theory, but is just abominable when placed next to comprehensive histories written by single authors. Toynbee and Trevleyan wrote such history earlier. And J. Roberts writes such history now, particularly his History of Europe, and History of the World, two models of lucid historical writing that make this disjointed compilation look like an ill-considered mishmash.

(3) It should have an audience. Or at least a different audience: the average intelligent reader wants a clean, interesting exposition of the important events and currents of the past. While some chapters achieve that, the most seem to be written not to the Average Reader, but to the Rival Colleague. And so we see a few facts casually presented, and then a sudden digression into some piece of scholarly minutae that leaves the reader (me, that is) pexplexed.

(4) It should teach historical knowledge, not assume it. This is one of those histories that assumes from the onset that you know all the relevant history. That might be OK for a narrow scholarly article, but it's an awful presumption for a comprehensive history. I read dozens of pages discussing the 'Domesday Book,' its importance, and its effects. The authors never thought to enlighten the ignorant, and explain what this Domesday Book was (an very old tax survey). Things like this litter every page.

From previous reading, I've learned that good history can be written. From reading this, I've learned that very bad history can be written, too.

This is a good book for a reader who is little like me. I have no training in British history and little in Western. I read quite a bit of history and don't mind a challenging work, though, which lets me get through most histories without too much frustration. This book often lacked the context with which self-teaching historians can teach themselves, even with frequent map- and index-checking.

The chapters of this book are all written by different authors, each one clearly an expert on the subject of his individual chapter. The authors do not agree on their audience. For instance, Gillingham's chapter on the early middle ages was clearly written, had several maps and followed a timeline before ending with a thematic look at the economy and political structure of the period. The very next chapter, Griffiths' chapter on the late middle ages, skips around by dozens of years within a single paragraph, mentions towns in France without maps and assumes foreknowledge of the battles of the Hundred Year war. Unfortunately, this book contains more chapters like the latter than the former.

I suspect that a European or an American with a basic familiarity of British history would find this a very useful intermediate level book with which to learn or re-discover an overview of Britain. The handiness of one volume written by many experts providing an overview of such a long history is what is right with this book. To those with some background in the subject, this book will be extremely convenient and useful. For someone without European geographic knowledge or a recognition of the figures in British history, even a patient and attentive reading will lead to frustrating hunts for the background of many important figures mentioned once within the narrative and to pointless searches through inadequate maps.