Errata for Programming Windows® Services with Microsoft® Visual Basic® 2008
The errata list is a list of errors and their corrections that were found after the product was released. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Date Corrected".
The following errata were submitted by our customers and approved as valid errors by the author or editor.
Color key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update
| Version |
Location |
Description |
Submitted By |
Date submitted |
Date corrected |
| Printed |
Page 25
|
Period not required
On page 25, the 2nd sentence from the bottom incorrectly contains a period in the middle of the sentence.
Change:
"However, the thread variable, or pointer to the thread, goes out of scope, and we .now have no way to directly access the thread and stop it from doing its work—or clean it up."
To:
"However, the thread variable, or pointer to the thread, goes out of scope, and we now have no way to directly access the thread and stop it from doing its work—or clean it up."
|
Microsoft Press |
May 06, 2010 |
|
| Printed |
Page 30 & 32
|
References to Thread.Suspend and Thread.Remove should be removed
On page 30, the "Ways to Control Thread Processing" contains references to Thread.Suspend that do not match the code samples.
Change:
"Thread Suspension
Our first attempt at thread control will be to use the built-in Thread class method called Suspend. This method will allow us to stop a thread in its tracks, or at least attempt to. A thread suspension can fail, in which case we would end up in a situation that we must code for—a rogue thread. However, for the purposes of this example, we will implement the Thread
Suspension and Thread Resume features of the Thread class.
Updating
We will use the method to suspend the thread; we will use to resume the thread."
To:
"Updating
We will use the method to abort the thread; we will use to resume the thread."
On page 32, the first paragraph does not reflect the code listed and should be removed.
The section to be removed reads:
"In Listing 2-18, we use the Resume method to start the thread back where it was suspended. You have to be careful about how your code handles being suspended. While the thread is suspended, you will receive no processing notifications. Therefore, thread suspension is not always the best solution. Let’s look at another scenario."
Microsoft Press is committed to providing informative and accurate
books. All comments and corrections listed above are ready for
inclusion in future printings of this book. If you have a later printing
of this book, it may already contain most or all of the above corrections.
|
Microsoft Press |
Jul 13, 2010 |
|