Rating: 
Summary: A great Resource to get your Service built fast
Review: A good book that is a valuable resource to quickly get your NT Service built. Good service control example code and explanations. Event Log examples and basic MSMQ examples. Example code needs to be modified to add MFC and CSocket support. If it had that, then I would have given it 5 stars.
Rating: 
Summary: Worth its weight in gold....
Review: After spending weeks in the MSDN labyrinth, trying to tie together the disjoint topics described, I found this book. It would have saved me much aggrevation and frustration had I found it earlier. The author ties together all the neccessities of an NT Service, installation, configuration, Event Logging, Security, LocalSystem, user accounts etc. in a clear, concise manner. The author does NOT dismiss related topics with the wave of a hand with the infamous "beyond the scope of this book" statement, but rather gives you a well founded background in them. i.e NT security and issues to beware of when working with services, an analysis of MSMQ and how to work with services, working with COM objects... I could go on, but you get the picture. If you are going to be working with NT Services, BUY THIS BOOK.
Rating:
Summary: Essential for Programmers AND Administrators
Review: After years of administering Windows NT Services the time finally came that I needed to write a service; this book taught me everything I needed to know about how NT Services work: not just with function prototypes, but with plenty of well-written examples, class wrappers for common tasks, and practical advice.Reading this book made me realize how much information was missing from all of the NT Service administration books that I had read (such as the NT Server Resource Kit). This book inadvertantly contains the best information on NT Service security, setup, registry settings, dependencies, startup, error logging, and other administration topics. Pratical advice abounds; after a section on the three ways to control service start order, Miller waxes, "...I can reveal that what you need to do in real life is almost never extremely complex. Most of the Win32 services you will write won't have convoluted interactions with other services. If the service will use RPC, for instance, you just need to make sure to specify RPCSS as a service dependency." That advice is very helpful to the beginning NT Services programmer that might be thinking about Load-ordering Groups or Tag Order for controlling service startup ( the most common route is Dependencies ). He continues, "The best advice I can give you is to keep it as simple as possible - use specific service dependencies rather than complex combinations of load-ordering groups and tag values whenever possible." Hope this helps.
Rating:
Summary: Value for money!
Review: Excellent overview on writing NT services. Most of what one would like to know about NT Services is available all at one place. Issues with NT Services, DCOM and Security are well covered. If u are dealing with NT services, go get this book.
Rating:
Summary: Finally, somebody pulled it all together
Review: I have fought the MMC, and NT Service security and permissions wars for the last time. For someone to write a book this good on a topic this diverse, he MUST be a genius. Especially if he can make the COM nightmare of the MMC snap-in interfaces make sense. Three Thumbs UP!
Rating:
Summary: Excellent Book! Don't hesitate!
Review: If you have worked in NT Service program field, you would have an experience to find an proper documents for real NT service program was so hard. This book cover all thing to make proper Nt Service. Really good book.
Rating:
Summary: This one is really good.
Review: It's hard to find someone these days who works with NT and is entirely unaware of NT services. There have been books treating the topic, there's some info and samples on MSDN, mag articles, and so on. Nevertheless, there have been two problems with all of it. First, all sources were treating services very narrowly, within a limited API-programming scope, and second--it was all over the place. This book imo successfully addresses both of these problems. It is most of what anyone would ever need on the topic, collected all in one place. Better yet, the author extends the coverage into lateral areas, from both the business and technological viewpoints. There's quite a bit on security, event-logging, COM and NT services interaction, MS message queue programming, ATL, debugging, profiling, and more. Quite a bit of that is useful even in its own right--services or not. You end up learning some, picking some suggestions, stealing code snippets from here and there... The book increases one's comfort not only with "hows" but also with "whys" of NT service programming. This may be the best book of the kind I've read lately. Which is not to say that it's perfect. Some passages, especially at the beginning, are somewhat unreadable. For some reason, "role" is repeatedly spelled with the French accent... There's been a few rather touching cases of split infinitives-evasion that resulted in what J.K. Galbraith once called "fine examples of fiduciary prose" that "the conoisseurs will want to read backward as well as forward." But not much of it! Not much at all... While on a few occasions the author did start to slide into OO crypto-shamanism--there's a few "patterns" and "semantics" here and there--he clearly managed to regain control of himself--the patterns theme is used reasonably, and not in an altogether inappropriate context. What else? In a few places "persist" was used as a transitive verb, which is annoying. Anyway, that's nit-picking. Let's concentrate on positives: there wasn't a single "refactoring" in all of the book! Not a single "cool" either. The words "remote" and "migrate" weren't used as transitive verbs--a feat unheard of in the realm of MS stuff-related tech writing. In fact, "remote" wasn't even used as a verb at all. I repeat, this book is the cleanest of the ones I've seen lately. A word about Wrox: While many formerly-trustworthy publishers, like AW, have obviously given in to the temptation and engaged in large-scale consumer fraud by throwing oodles of nonsense, pseudo-scientific OO-puffery at the reader, Wrox seems to be quietly establishing itself on the level with O'Reilly. Good for them. Thanks to the author and the publisher.
Rating:
Summary: The way complex subjects should be treated!
Review: Knowledgeable and complete explanation of importance and use of NT services. Every "How" has concise and understandable "Why". Chapter about NT security, general tips for multithreaded design, MSMQ, ..., a lot of extra staff. Elegant C++ classes for every aspect of NT service development - immediately reusable. Worth every penny you'll pay for this book.
Rating:
Summary: The way complex subjects should be treated!
Review: Knowledgeable and complete explanation of importance and use of NT services. Every "How" has concise and understandable "Why". Chapter about NT security, general tips for multithreaded design, MSMQ, ..., a lot of extra staff. Elegant C++ classes for every aspect of NT service development - immediately reusable. Worth every penny you'll pay for this book.
Rating:
Summary: Chapter 5 - Event Log Class
Review: Mr. Miller wrote a handy class for event logging called CEventLog, but he chose to use overloaded names for the methods to handle all sorts of different types of events. If I were you, I would NOT do this. Instead: I would give each LogEvent() method in that class an explicit name, because it makes it more clear which method will be invoked. In my particular case, I sort of assumed his class was good until I noticed that a bunch of my custom messages weren't printing to the event log. Because it was 2:00 AM when I found this, it took me a long time to figure out the problem. Anyway, the rest of the book is pretty great, a must-have if you're going to be writing a service.
|
