Errata for Programming .NET Components

The words "camel" and "Pascal" HAVE BEEN SWAPPED.

"Another form of component used by outside entities besides object instantiation and method calls is inheritance." NOW READS: "Another way components may be utilized by outside entities besides object instantiation and method calls is inheritance."

"Reflection is particularity useful..." NOW READS: "Reflection is particularly useful..."

"A multiple files assembly, on the other hand, has much more latitude in how to compose it all." NOW READS: "A multiple-file assembly, on the other hand, has much more latitude in how to compose it all."

"The object should channel the implementation of both Dispose() and Finalize() to same helper method ... NOW READS: "The object should channel the implementation of both Dispose() and Finalize() to the same helper method ...

"This is done using the C# param parameter modifier ..." NOW READS: "This is done using the C# params parameter modifier ..."

"Binary Operation" NOW READS: "BinaryOperation"

"return = num1/num2;" should be: "return num1/num2;"

"..., the exception will be handled as the worker thread from the thread pool, an you will never know about it." NOW READS: "..., the exception will be handled in the worker thread from the thread pool, an you will never know about it."

The reality is, of course, that the subscriber can't tell." NOW READS: "The reality is, of course, that the publisher can't tell."

"The technique shown [...]: you use the param modifier to pass in any collection of arguments, as well as the delegate containing the subscribers list." NOW READS: "The technique shown [...]: you use the params modifier to pass in any collection of arguments, as well as the delegate containing the subscribers list."

"This implies that for every asynchronous method call, there is some overhead in terms of memory use and performance .NET supports defining fire-and-forget methods, using the OneWay attribute, which is defined in the System.Messaging namespace:" NOW READS: "This implies that for every asynchronous method call, there is some overhead in terms of memory use and performance. As an alternative, .NET supports defining fire- and-forget methods, using the OneWay attribute, which is defined in the System.Messaging namespace:"

InvokeDeleagte" should read: "InvokeDelegate"

"to the native operating" NOW READS: "to the native operating system"

"even if the sleep timeout is less than the reminder of the time slot." NOW READS: "even if the sleep timeout is less than the remainder of the time slot."

... in this case) and avoid ... NOW READS: ... in this case and avoid ...

"(as far as the operation system is concerned)." NOW READS: "(as far as the operating system is concerned)."

"The Set() method sets the state of the handle to signal" NOW READS: "The Set() method sets the state of the handle to signaled"

<SOAP-ENV:Body> NOW READS: </SOAP-ENV:Body>

"ISponsor.Register" NOW READS "ILease.Register"

"/Register the sponsor" NOW READS "//Register the sponsor"

"..., expect that the" NOW READS: "..., except that the"