I'm attempting to write a hard boiled mystery and I've read almost everything I can get my hands on on crime and writing.

This is a great book cuz it has short, informative chapters and also suggestions on where to get more information.

My only complaint/gripe is that he doesn't explain the jargon in a few places. I felt I could have used a few more examples in order to truly understand what he was getting at. Jesus used parables -- and look where it got him!

This book covers some topics such as code access security really well but others like ASP.NET security really badly.

The ASP.NET section is almost useless - so few pages and so little information.

It would have been better if the book had been called .NET code access security and didn't bother with the other stuff.

This book is an excellent starting point for understanding the .NET framework security mechanisms. Especially code access security.

Its only real failings are the lack of depth in a few obscure areas (details around simulating permissions that might be granted to an app deployed via the Internet and hosted in IE).

You could glean most of this information from the internet and spend a month doing it, like I did. Or spend $$$ and few hours reading this well written book.

Make no mistake,as you will get your hands wet programming Micrsosoft's "managed code" (C#, VB or ASP.NET apps), you will eventually encounter the all pervasive and extensive security system that is integrated in .Net.
This book is the definite security reference and guide to the new programming platform that Micrsosoft has shipped - and the only book of its kind on the market as far as I can see. It has been written by the people who have designed and implemented the security features and infrastructure in the .NET Framework that ASP.NET, C#, VB or Managed C++ applications run on.
Its stuffed with sample code and hands-on tips, and comes with extensive sections geared specifically towards developers and admins. Chapters are well contained and you get the kind of insider information only the people who have actually build and designed the system would be able to give you.
800 plus pages of security information for the Amazon price is quite a good bang for the buck,so I highly recommend this book as I think it will be a good learning aid in trying to understand .NEt security and remain valuable as a reference work afterwards.

I just finished the shelf exam having studied this book exhaustively, and I honestly think there's simply too much detail. Endless questions on the details of Riley-Day syndrome, McCune-Albright syndrome, and parasites found only in Africa. The test was certainly not easy, but the bulk of it dealt with the more common diseases like Henoch-Schonlein Purpura and Rocky Mountain Spotted Fever. I'd go with blueprints first and foremost, maybe supplement with a question book like this one and don't get too caught up in the details of obscure diseases.

In addition, some of the questions are just plain wrong now, such as questions on vaccination recommendations that are out-of-date.

Overall, I'd still recommend this book, so long as you don't get too depressed over not knowing the hardest questions.

I found the book to be a detailed, yet concise review for the boards. The material covered is excellent, but the questions do not reflect the USMLE format.

The book was published in April 2000, which means it was probably written during late 1999 and early 2000, when the NASDAQ was soaring to 5000 and tech had no boundaries. Its tone of breathless enthusiasm is very representative of that time. The book does accurately state the e-potential, but like NASDAQ investors in March 2000 did, it extrapolates unsustainable trends into a ceaseless upswing. The Web is here, and it is a true revolution, but ultimately it is simply another communication channel for insurers and their stakeholders. This is a great read, but only to help understand what kind of carried-away thinking created the tech bubble.

The quality of pictures and diagrams were poor. More slide preparations should be displayed