Visual Basic .Net Windows Services Handbook

by Richard Conway, William Sempf, Brian Patterson, et al.

Windows Services are an often-used and important tool that can be used for anything from a simple service that monitors when a file changes, to a complex application that provides resources for system... This description may be from another edition of this product.

• Format: Paperback
• Language: English
• ISBN: 1861007728
• ISBN13: 9781861007728
• Release Date: October 2002
• Publisher: Wrox Press
• Length: 350 Pages
• Weight: 0.70 lbs.
• Dimensions: 0.5" x 6.3" x 9.3"

Customer Reviews

Windows Services Served Well Done

If you like Windows Services, you'll enjoy this handbook. As an entry-level systems administrator, I wasn't exactly sure how I could leverage .Net. I was taught C and C++ for windows services, but not everyone wants to learn, peer review, and maintain that.As for the handbook, each chapter did a nice job of keeping my attention (that's good seeing as how I'm a generation X'er) and the overall structure, prose, and subtle humor kept me glued to each page. Visual Basic .NET Windows Services Handbook gave me direction and purpose regarding future .Net services on our company's infrastructure. This handbook is a great tool for setting your sail in the seas of .Net Windows Services.

Excellent: for professional programmers and in education

The book is kept short and precise, very well structured. It fills a lots of gaps currently open in MSDN. It's the only one book you need for writing professional Windows services. Highly recommended.

A Good reference for authoring windows services

I read through this book in one go and found that it serves as an excellent reference for those who would like to author windows services using the .NET framework. This book has been well organized, starting from the ground-up, explaining the anatomy of a windows service and goes on to cover advanced topics like threading and installation. A must have for people who would like to write windows services. I hope they would come up with a C# version soon (but C# guys can still use this one as a reference).