Microsoft Books

Code complete is the right title for this book. Sadly most people find it extremely hart to read it. Its great as a reference but reading it word for word is as interesting as watching grass grow. Don't get me wrong. This is a great book. Everyone should at least hold it for once. But do not try to read it as a book. The first 300 pages will be boring. When the actual code chapters begin it gets better but still tends to be tedious.

A great book for beginners but a little boring read for advanced users.

When I bought this book, I couldn't believe all the 5 star ratings in the reviews. But, now that I've finished it, I have to agree with them. Simply put, this is probably the best computer-related book I've read. In the book's 850 pages, I found a grand total of five minor problems: one was grammatical, two were typographical and two were minor disagreements with how some things were presented. All trivial. Content-wise, if the universities would teach this material and if programmers would follow the methodologies contained in the book, the world of software would be far, far better off. I HIGHLY RECOMMEND this book and rate it an Excellent 5 stars out of 5.

This was a great book both for me and my team. I've been in the software industry for many years. I started building a team of developers and needed an easy way to bring novice and experienced programmers together on a similar set of standards. This book provided us with the perfect framework from which to start our team. We've developed several major projects using the principles in this book and have experienced a great deal of success.

One warning, the book gets a bit tedious after the first half. If you're looking to improve your C programming skills, it gets really detailed into pointers and other fun, or not, stuff. Also, the examples are in VB.NET...but you still get the point.

If you're an experienced software developer or a newbee in the world of commercial computer programming this book will give a good kick in the right direction. Steve McConnel will keep you hooked by mixing the right guiding concepts with real-life knowledge and examples.

for all programmers. Shall I say Application Developers? Software Engineers? Whatever the title is, programming jobs are alive and well! This book provides a solid foundation. It is too bad very few American students are interested in this profession.

The average students are all studying business marketing. The good students are studying finance.

At Harvard University, they do not teach Accounting. The best ones, study Economics. There are only 21 students studying Computer Science at Harvard. Yet, parents are paying $220,000 to Harvard and other Ivy League. Truly amazing!

Is there anyway we can change this trend?

Firstly a warning, this is the second edition and covers Windows 2003. There is a third edition that covers the newer OS. I bought this book by mistake and it's too big (postage would be too expensive) to return. So buy with care.

This is a big book in terms of pages but the content is less than stellar. Don't expect to find too much on designing AD in real world situations such as integration with networking topologies and devices. Nor expect to find details on integrating AD with other Microsoft technology such as SharePoint. No this cookbook is really an administrator companion, and I think it does a pretty decent job in that but not more.

Very handy cookbook reference for my office bookshelf. I've used it a number of times, and it's more than paid for itself in expediting regularly-scheduled inquiries of our AD structure here at GEICO HQ.

Excellent reference if you work with AD on a regular basis either as an admin or a developer. Each "how to" offers methods for manually performing a specific task as well as (where possible) how to automate the task using code. Should be on every Windows admin/developer's desk.

Overall, this is a great book for reference.

There are a number of areas where I think the book falls short - all of the scripts are very hard coded scripts that don't tell you how to do some functions that would make their scripts actually useful (like "pull the list of users with attributes from a tab-delimited file and create them" or something similar, this would make mass creation of users actually useful, instead of "create user1, user2, user3, etc..."). I think that the writers expect you to be a VB expert (or at least close to it) if you're going to actually make the vb scripts useful.

Most of the scripts are "How to use a script to do the same functions that you can already do in AD with ADUC or another MMC", but I think that the most important thing for me about the book is what it inspires me to think of doing. Things that MS doesn't necessarily expect you to do. I'm still not seeing a way to add sidHistory to an object (MS does it with another applet - there is a way...), but there are so many things in the book that just have me thinking about how you can implement changes to an environment that MS says you can't do. What they really mean is "You can't do that with the GUI tools that we provide you".

I am so glad that this book was recommended to me by a guy I took a class on scripting from. I use this book everyday (almost). I even took it on vacation with me for light reading.

All the features of WPF are explained here, with samples and visual codes for your reference. I decided to buy this book and other about Blend 2, but most of my doubts I solved with this edition.
Great book from beginners to experts.

Hey, a programming book in full colour!! WPF Unleashed really does introduce the concepts and details of WPF programming in a clear and easy manner, and Adam Nathan is to be commended for his efforts. Anyone wanting to learn (more) about WPF will benefit from this book.

This is a well written, well structured book.

Full color with good examples and covers a good range of details.

What can I say.. I was looking for a book about WPF. I saw many, and many until I found that one. Then I stopped looking for more :)

On first opening this book you are struck by the beautiful full colour pictures and syntax-highlighted code samples. [Though the experience was slightly marred by the tears and damage to the front cover which occurred during shipping, as was also the case with another book in the order.]

I did a quick flip through and thought... "Beautiful presentation, but the content looks a bit over-simplified. Maybe all the reviewers were seduced by the full colour pages."

Then I started working my way through the book. I was blown away. The writing style is simple and to the point. But it doesn't lack depth. There are indications of the little things that are likely to catch you out, as well as discussions of some pretty advanced topics too.

So, Yay! The content of the book was just as good as the way it was presented, if not better. My only criticism is that in some cases there could have been more code examples.

On the other hand this would probably have made the book very bloated and not as useful as a reference book. There's enough information to point you in the right direction, and from there google will get you to all the code samples you need.

So let O'Reilly do the cookbook style books with lots of code snippets. They do that so well. This book takes a novel approach, and it works brilliantly!

I bought the first edition of this book called Programming Windows Presentation Foundation (AKA Avalon) at the PDC in 2005 and read it completely on the plane home.

When I heard the second edition was released I didn't think much would have changed, but this is even better than the first edition. It's twice as big and covers all major (and not so major) topics in WPF (inc. an introduction to 3D and Silverlight).

I think this book will proof to be for WPF what Programming Windows, Fifth Edition is for WIN32 programming.

This book is the most in depth resource into WPF i have seen. And not just that, it gets to the good stuff that you'll actually use in your code and not just filler or lists of properties that you can get from intelisense. The examples are extremely useful.

The other benefit of this book is that it doesn't just tell you how to do things, but why. This is incredibly helpful in finding the best solution to your specific problem.

Thanks guys! great book!
Ralph

I say to ignore those reviews because they do not refer to this book. This is the second edition published August 28, 2007 with 863 pages. Those reviews are based off of the first edition published nearly two years before (September 12, 2005) and with only 447 pages.

Using Amazon's 'Search inside this book' takes you to the 2005 edition also. That shows only 10 chapters while this edition has 17. Most of the negative comments from the 2 and 3 star reviewers seem to have been resolved.

The biggest strength of this book is that it focus on using WPF programatically, not just laying out XAML. This is extremely useful if you are writing an application for 3D data visualization or a database driven application. You get to learn to create event handlers, generate meshes... all programmatically. I also believe that this book is great, not just as a learning tool, but as a reference guide. It is the most comprehensive book on the subject and a must for the aspiring WPF developer.

If you just want to focus on XAML, however, I will have to recommend "Windows Presentation Foundation Unleashed" by Adam Nathan.

As a software developer I've written tons of production-level code for many companies including Rockwell Automation, Compuware, MS.
And I found this book to be too shallow for a technical person like me.

[One can save money by simply downloading WPF SDK samples and learning them]

Can one design and implement a better than WPF framework after reading this book? Obviously not!

No wonder, the authors never developed significant portions of any known product/framework!

Also, my e-mail exchange with C. Sells indicates that he himself doesn't really understand WPF in depth.
(BTW, as a MS employee he has luxury of having access to WPF source code and symbols - he obviously didn't bother to do so)

Just a few examples:
-- Managed/Unmanaged transition, e.g. the MIL stuff
-- Lack of understanding the WPF control model
-- Lack of understanding the WPF text model
-- Just like in any other *shallow WPF book* [are there deep WPF books out there?] authors make no effort to scrutinize the existing framework (WPF). [Which is definitely far from being clean and nice]
-- WPF "GDI-free" claims are nonsense since WPF uses User32 and User32 and Gdi32 libs are tightly coupled.

I have a friend that recommended me this book and I have to agree with him that this was a very well written book. Don't let the fact that the title says "Windows NT" discourage you from getting this book. There is a lot of useful information in this book that is still standard practice for scripting in Server 2003. Probably one of the few and only outdated commands in the book is the AT command that was replaced by SCHTASK. Even then, the author goes into detail on how these different commands work and how to use them in your work environment to you benefit. I recommend this book as a learning tool and as a reference for my fellow scripting brethren.

Great book on NT shell commands that Microsoft doesn't even document. Not even "command /?" gives you any help.

Great for reference and to learn.

Although this book was authored in 1998, it is still as relavent today with Windows Server 2003 as it was when Windows NT 4.0 was first released. The fact is that the Command Shell hasn't changed all that much over the years and Timothy Hill's book remains the best guide to using and writing command scripts that I could ever recommend. And with Windows Server 2003's push to be able to do everything from the command line that one can do from the GUI, it's even more important to fully understand how the Windows Command Shell works.

Windows NT Shell Scripting is less about Windows NT than it is about how to write shell scripts. It covers the details of using the Command Shell in interactive mode, its configuration and how the 32-bit Command Shell differs from the 16-bit DOS box. Then it delves into the structure and syntax of the Command Shell language, providing a clear understanding of how the program control features such as IF and FOR work. Finally, it shows you how to create sophisticated shell scripts using the internal commands and external command-line utilities included with Windows and their Resource Kits.

Not everything in this book has survived the test of time. The old task scheduler using the AT command, though still supported in current version of Windows, has been mostly replaced by more powerful Scheduled Tasks of Windows 2000 and later. And you will want to supplement this book with a modern reference of the utility programs available for Windows XP and Windows Server 2003 (such as OReilly's "Windows Server 2003 In A Nutshell"). Yet this represents only a small part of the book and majority of material stands up very well. Certainly there is no better and more in-depth tutorial for building command scripts than Timothy Hill's book.

I like this book because unlike many technical books, the first three chapters aren't a pedestrian introduction to the basic fundamentals. This book spends chapter 1 with insight, similar to the way Applied Cryptography immediately gives you knowledge. I'm an experienced NT command shell user, and this book was valuable for me as well.
The DOS shell has become a requirement and skill relegated to the background by the direction of Microsoft curriculum, this book explains it and teaches it.

The authors instructions are easy to follow, without doting like the Teach Yourself "whatever" in 24 hour books, Tim Hill doesn't waste your time, or your money.

If you have a bit of programming experience, this book together with access to the NT Resource Kit tools will provide you with the foundation for doing almost anything you could imagine within Windows NT Shell Scripting.

The book can be used both as a tutorial and a reference for Windows NT scripting and gives good examples of the commands, tools and concepts covered. For Windows NT, this book does the job as your Shell Scripting Bible in less than 400 pages.

Since Windows NT 4.0, a lot has happened in the Windows scripting field though. With the release of Windows 2000 and the subsequent Windows XP and .NET Server, shell scripting has become much more powerful. A second edition of this book covering the new commands and tools would be most welcome. Until one exists, you might also want to look at newer books covering shell scripting for operating systems based on the Windows NT kernel.

You might also want to look at other, often more powerful ways to script your Windows NT-based environment. For that matter I recommend looking at other books covering WSH (Windows Script Host), ADSI and WMI (Windows Management Instrumentation).

great read about taking chances, following your heart and making a difference. if this story doesn't inspire you to reach out and help your community, you probably are too self absorbed. better written than three cups of tea.

after having read this book, i decided to change my life and leave my job at one of the world's largest hotel companies, where i had a nice job, making a lot $, but no satisfaction in life. a career? I wanted a Calling, which is what I now have.
not a day goes by that I am not thankful for having jumped at the chance to change my life, for the better.

The true account of a man who gave up a dream job and the business fast track, security, a personal life, and his dream of owning a house to build libraries and schools in the poorest countries and stock them with books. A caring and brilliant businessman. An inspiring and brave story. I love the way he thinks and writes. I had one question throughout the book. Mr. Wood thought he had enough money saved to support himself for about five years. More than five years went by, but he didn't mention how he continued to have the money to feed, house, and clothe himself. He never mentioned collecting a pay check or receiving personal donations.

Very inspiring. If you liked this book you will love Three Cups of Tea which is a similar story, but written by a man who started with nothing at all and hadn't the faintest idea how to proceed with building schools.

Like a 2-out single that sparks a multirun bottom-of-the-ninth comeback, John Wood's story is most exciting due to the couldn't-have-seen-that-coming factor. What started as a vacation turned into a small idea, which exploded into one of the coolest charities I've read about. In fact, I was so inspired by this story that I wrote to John Wood immediately after I was finished (requesting a job because we know where Sp... ah.. my company.. is headed).

But what is the story?
In Leaving Microsoft to Change the World, John Wood is on a small sabbatical (in Nepal) from blossoming Microsoft. There, he discovers the country's intense need of books, libraries, and schools and its childrens' more intense desire to learn. He promises to return with books (on top of the pictured yak). What follows is an absolute eruption of giving from John's friends and family. Funding and providing books for one library soon turns into John leaving his killer position at Microsoft to work on his charity full time. Now, Room to Read (the charity) is present in seven countries in Asia and Africa building libraries, schools, and funding education.

Not just a success story...
Perhaps the part I enjoyed most about the book is that it does not only talk about how his charity started, but it discusses entrepreneurship, management theories, and other business ideas. It seems that business lessons learned by John apply strongly to successful for-profit organizations as well. Perhaps what stands out the most is how lean, focused, and passionate his company is.

Anyone can do it
As long as you've, you know, worked at a skyrocketing tech company, have millions of dollars of stock options, and the ability to quit receiving a salary for years at a time and still travel to third world countries. Admittedly, the author talks about how anyone can get involved, but it sure makes following your dreams easier when you've got the money to do so.

"It will make you want to quit your job."
Well, I was warned (Jeff) before I started to read that it would make me want to quit my job. It's true, a social improvement job is a lot more appealing than SQL. Leaving Microsoft starts out interesting and only improves. It is not a particularly difficult read, either, so that, coupled with how much fun it is to see Room to Read succeed makes this a rather quick read. At best, you'll be inspired to "dive in" (the author's words); at worst, you'll be entertained for a couple hours' worth of reading.

Leaving Microsoft to Change the World Rating: 84 / 100
Writing Style: 7 / 10
Finish-the-chapter-before-bed Factor: 8.5 / 10

Very well written book. Enjoyed reading it, and finished it in two days. John Wood has done a tremendous service to Nepal and Cambodia (two countries in which I used to live and work). Amazing work that needed to be done. Great reading also in the book about some of the inner workings of Microsoft as well. Read this book!

This book "flows" easily and it does a great job covering the meteoric rise of both Bill Gates and Microsoft. The narrative is never dull and both, the man and his company, are given a fair treatment. This book was published in 1993 and a lot of interesting stuff remains to be told. Wish the authors would team up for a sequel. This is a well written and authoritative account of Microsoft and its founder.

Hard Drive: Bill Gates and the Making of the Microsoft Empire

This book is a must-read for people who consider themselves ambitious and driven. It taught me the importance of single-minded drive and determination, coupled with a passion for the line of work one is in. IT is a tough line of work to be in - jobs could be outsourced anytime, skills become redundant quickly and there isn't the glamor or get-fabulously-rich possibility of finance or investment banking... but this book demonstrates that as long as you are passionate about what you do, there is always room at the top. Take heart from it!

This is the definitive Book about Bill Gates (and the history of Windows). It covers all the management aspects of how he drove Microsoft and how the work became his life. The man doesn't do business... He LIVES it. And this book describes it in very much detail.

The details includes how Bill "turned over" IBM... Promissing them the OS/2 under the "NT Technology" flag and how he realeased Windows 95 and killed IBM forever from the Desktop business. It also shows Gates apreciation for Older woman (and many that took him to bed). As part of this "private" package, it also explains the problems that He had with Steve Ballmer. How Ballmer was showing poor management and leadership under Gates perspective and how Ballmer got over it and made his loyalty to Gates forever.

I was more interested on the part that explains how Microsoft Windows 1.0 was developed. How disastrous the first Office was compared to the competition and how they managed to "work around" and fix it, by "coping" the competition and improving it "the Microsoft way".

Buy this if you want to know how business can be done... or be "copied".

Delightful book. Its one flaw is its addictiveness, I couldn't put it down which did cost me sleep (I'm an IT professional with an entrepreneur spirit- your results may vary).

The Microsoft/Gates biography is impeccable in its wealth of interesting details and engaging story-telling.

Bill Gates is a fantastic decision maker. He would be as successful selling water or space suits, he just happened to be at the right time in the right booming industry and pushed with his business-business mentality to the limit. Right decision after right decision, the Microsoft journey is a story that any entrepreneur should nitpick and absorb as much as possible.

Of course, his terrible capitalistic drive is a perfect subject for a discussion on morals, social responsibility and related matters, but without a doubt when it comes to maximizing outcome while playing by our economic rules, Hard Drive tells a tale of epic proportions featuring a superhero / villain that rivals the best of science fiction.

This is really a story of how Gates led Microsoft to its apex, ending in about 1992. It is well written and a good balance bewteen criticism, an explanation of the business model, and historical detail. The story is, to put it mildly, remarkable no matter what you think of MS and Gates.

While a student at Harvard in December, 1974, Bill Gates III and Paul Allen informed Ed Roberts by telephone that they had invented a BASIC computer language for the MITS Altair 8080, which was the first "personal computer" kit for hobbyists. Could they license it along with each Altair kit, Gates asked, to customers for a royalty fee? It was an audacious proposal, because not only had Gates and Allen invented no such thing, but they neither owned an Altair kit nor did they even know the technical specifications for the Intel 8080 chip. Skeptical of their claim, Roberts replied that whoever demonstrated a working BASIC would win the account: Gates and Allen were in competition, he told them, with 50 other "geeks" who already had made the same claim. Gates and Allen then hunkered down for 8 weeks to write the first BASIC for a microcomputer. The resulting "software", which immediately won over Roberts, was the first application of what would become Microsoft BASIC. Gates was 19.

As the company founders, Gates and Allen shared a vision that virtually every home and every office desk would eventually have a PC on them, all operating with their software. To run Microsoft full time, Gates dropped out of Harvard in January, 1977. Their business quickly expanded beyond the Altair as competing brands of personal computers emerged, including the Tandy from Radio Shack and the Apple II computer; they were also called upon to program BASIC into a number of other electronic devices. All along, Gates' goal was to gain market share, in effect setting the software standard for most, if not all, PC users. As a true believer who intimately knew the product, Gates was the principal salesman, while Allen concentrated on technical development.

During this formative period, Microsoft's corporate culture was established. Perhaps as a result of hiring many of his programmers straight out of university, Microsoft's offices (and later the campus in Redmond, Washington) took on the look and feel of a college campus, that is, an informal and a freewheeling intellectual atmosphere with "late hours, loud music, walls full of junk, anything goes dress, Coke, adrenaline, unbuttoned behavior." Employees tended to be very young with a programmer or engineering mentality; they designed their products for tech-savvy customers - male in their early 20s - like themselves, a kind of fellowship for computer adepts. Like Gates, they loved to play with and program electronic gadgets.

Microsoft hired the brightest programmers with demonstrated practical abilities. Employees were also expected to work extremely long hours as a team toward a common goal, not as strident individualists. Gates encouraged them to develop their entrepreneurial passions, forcefully advancing their own ideas of useful products for new markets. Overseeing it all was Gates, who gained the reputation of a harsh and challenging critic with a relentless drive for excellence, whether to beat the competition or out of fear of falling behind in such a fast-changing industry. As the sole remaining founder after Allen's departure in 1983, Gates remained deeply involved in both technical and business details as well as the general direction of company strategy. Nonetheless, as the principal revenue generators, Microsoft's product groups increasingly became the seats of decision-making power, in spite of Gates' active engagement.

At the end of 1979, Microsoft had $US 4 million in sales. Most of these revenues came from BASIC, which enabled programmers to create applications, such as word processing and accounting spread sheets. The level below BASIC and the other languages under development at Microsoft was the computer operating system, which performed the most elementary tasks required to run computers. With the prospect of providing software to IBM for the basic PC it was planning to market for a reasonable price, Gates and Allen began to acquire the rights to, and then develop, software for a computer operating system. Known later as DOS, it again set an industry standard that would enable Microsoft to efficiently develop languages and software applications in a single engineering environment rather than painstakingly customize them for a variety of incompatible operating systems. This would immensely simplify Microsoft's programming process as well as enhance its efficiency.

As Gates foresaw, this was a near-ideal position to occupy at the moment that the PC market was poised to grow explosively with the introduction of the inexpensive IBM PC, which was made of off-the-shelf components and hence easy to copy, or "clone". With the dual ownership of DOS and several major programming languages, Microsoft became one of the fastest growing companies in the world. By 1985, just prior to its IPO, on revenues of $US 140 million, Microsoft had a pre-tax profit margin of approximately 34%, no long-term debt, and cash reserves of $US 38 million. By 1987, the company surpassed Lotus to become the world's largest software vendor for PCs. Gates was on his way to become the richest man in the world, at least for a time.

However, the ownership of DOS and the programming languages would also, critics later claimed, confer an "unfair advantage" on the company. First, the Microsoft applications groups were accused to obtaining "inside information" from the operating systems group, which enabled them to design their products to function more quickly and smoothly than competitors could. Second, because each change in DOS required competitors to supply their latest products to Microsoft programmers to ensure compatibility, critics charged that this amounted to an inside peek into their strategy at the cutting edge of their capabilities. It was a symbiotic relationship that made many outside vendors - independent companies developing applications to run on Microsoft operating systems -uneasy and resentful. Third, DOS programmers were accused by rivals of inserting "hidden bugs" into the operating system in order to hinder the function of competing products, such as the Lotus spread sheet, damaging their competitive position and brand. The resulting negative publicity did a great deal of damage to the Microsoft brand, which began to be seen as the industry bully.

While Gates insisted that he had erected a "Chinese Wall" between Microsoft's applications division and its Operating System's Group, it was not enough to deter the Federal Trade Commission (FTC) from opening a probe into the company for anti-competitive practices that purportedly hurt consumers. By 1991, when the FTC probe became widely known, Microsoft controlled one-quarter of the applications market and dominated the operating systems market with Windows. There was speculation about the imminent breakup of Microsoft into separate companies for these markets, similar to the dismantlement of AT&T. For their part, defenders of Microsoft argued that it was winning because it was better and smarter, presenting its customers with superior products at bargain prices.

This a pretty much where the book stops, which badly dates it. Not only is the story of the anti-trust law suits left untold, but subsequent business developments - notably the internet - are not even mentioned. Thus, this is an excellent early history, but the reader must look elsewhere for more detail. Of the shelf of books on MS, in my opinion this is one of the best, and it was most useful to me for a research project. Recommended.

Since my book is older, it was a used version, the hints are for older things. It does have some helpful tools, but lots of the annoyances, I already knew about.

This book is written in a very easy to understand language. The hints are pratical and should help everyone in some way. Microsoft will not tell you much of how to make your operating system work the way YOU want it to. Steve Bass takes care of that. It is a valuable resource for anyone who has a PC, novice or experienced. I consider myself somewhat knowledgeable about computers and I even learned a few new tricks.

I am still pretty much a neophite where computers are concerned, so I bought this book hoping that it could get me out of the "messes" I'm always getting into. It really DOES help! Thank you!!! Steve Bass, I'm now searching for other books you have written.

This is the first computer book I actually said down and read, cover to cover. It holds your interest, and each tip gets you excited for the one to follow. I call it my AHA book. All the time you read it, you go "Aha! That's the problem!" or "Aha! That's how to get rid of that!". Can't recommend it highly enough.

I've read many computer books, and I have to say this is one of the most informative. More important, Steve provides hundreds of tips to overcome the small (and large) problems of Windows. It's nice to konw that even a well-known computer columnist experiences the same frustrations we ordinary users do. Happily, he willing to share the solutions he's found.

In my first reading, I discovered the answers to at least 7 windows annoyances I've encountered.

And instead of including a cost-raising CD, the publisher has made 100 utility programs available online, a better solution that including them on a quickly outdated disk.

A useful, and often amusing book.

You need it!

If you want to know what is going on under the hood, thn this is THE book.
Every chapter is very in depth with good examples. Definite YES for the geek inside you. 5 Stars.

I love reading Richter's books. When you think that there's no room left for improvement you get a title like this one. Wow!
Where other books present the subject matter this one gives you knowledge. Improves on the previous one.
Covers new topics like generics or nullable types. Just can't wait to see what Richter will do with linq!

I'm more of a Java and Ruby developer, but I found this book fun to read anyway. It's a great read to understand how languages interact with core libraries and how it all fits together inside of a virtual runtime environment. Very well done.

The book is oriented toward experienced programmers. It provides an introduction to the CLR and describes some intermediate topics in detail. Advanced topics are mentioned, but the coverage of advanced topics (such as CLR hosting) is shallow.

If you are an experienced programmer who is new to the CLR and C#, this is a great text. If you already understand the CLR and are looking for more information about advanced techniques, this book is probably not for you.

Most of what needs to be said about this book has already been said. But I feel a need add my two cents, if only to toss another five stars out there.

Really, this one is an example of what a good technical book should be. It's style is both understandable and unpretentious and it covers topics with depth and clarity. The overall organization is such that it never seemed like that terms, ideas, and concepts were being used that had not been introduced previously. Reading this book was a true pleasue and I know I will be referring back to it many times.

The book provides a developer's view of the internals of the .Framework and its CLR. It's more than you need to know to hammer out a lot of code. But if you want to build really good apps - or just want to know what .NET is all about - buy the book, read it, and keep in at hand.

Woody's book (and WOW site) offer the very best practical and error-avoiding advice on using MS Outlook 97. Using Outlook is very different from using other Office applications. The file management aspect is thoroughly confusing and inflexible. Woody's book helps deal with this thorny issue.

As a software trainer and consultant, I am always looking for good books. This book is not good -- it's GREAT! The information on pgs.643 to 647 is worth much more than the price of the book! A must have....

Until now I have practically only been reading the Outlook 98 part of the book, as this part was the most urgent from my point of view. I have certainly not been disappointed. But on the other hand I had not expected less as a keen reader of Woody's Office Watch (WOW) and Woody's Window Watch (WWW). I am really looking forward to the rest of the book. It is a pleasure reading and learning from a book where there are a lot of humour included.

I have been using Office 97 for 1 1/2 years and have taken college courses in Word 97 and Excel 97. Having received certificates in both courses I thought that I knew it all. RIGHT! Woody Leonhard has taught me about the easy ways to execute commands. His shortcuts are invaluable to me. I am a quadriplegic and find his advice very helpful and time saving. I am learning Powerpoint 97 in far less time than it would of taken me in school. I believe he has been most helpful in making me a real power user. Thanks to Woody and his gang.

Clear, concise and easy instructions on how to use MS Ofc 97. Points out the good, bad and ugly of Microsoft products. Can turn any novice into more of a professional than he/she ever dreamed of! I recommend this book to anyone who will be working with MS Ofc 97! Don't pass this one up!