Weak, but nothing else is out there.

This book is full of problems. Unfortunately I can't point to anything better.

From the chapter about Windows Services:

"Windows services, I'd like to point out, is a bit of a misnomer, as this same functionality is also available on the Mono/Linux platform using what is called a monod, which (I believe) is an implementation of a forked daemon and has nothing to do with Windows at all. I am also pretty sure the other .NET-implemented platforms don't use Windows in any way to implement the functionality. Admittedly, I have not looked into it. Personally, I think Windows services should be called service processes, as the implementing .NET Framework namespace suggests."

What is the author doing making pronouncements riddled with "I believe", "I have not looked into it", etc.?

Furthermore:

"Also, due to the fact that the Windows service has no interface, it is ideal for running in the background thread on a server. Since I do not cover multithreading until later in the book (Chapter 16), I will not the cover placing of a Windows service in a background thread, but after you have read Chapter 16, you should have little difficulty doing so."

If the services are ideal for threading (which they are) why is the chapter on threading deferred until after the chapter on Windows Services? Why weren't threads covered, and then the services could be covered including threads?

The whole book reads like this. It's a superficial reading at best.

Other Reviews

• Pro Visual C++/CLI excellent book!
• Not the book I'm looking for
• Weak, but nothing else is out there.
• Be cautious!
• If you purchase just one book on C++/CLI, make sure it's this one