The errata list is a list of errors and their corrections that were found after the product was released.
The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.
Color Key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update
| Version |
Location |
Description |
Submitted by |
Date submitted |
| Printed |
Page 15
Figure 1-3 |
The box labelled "Simple web services" should arguably be "System.Web.Services", in
keeping with the namespace names in the other boxes, and given that "Discovery",
"Protocols" and "Description" are all sub-namespaces of System.Web.Services.
(code)
The file Sampleschapter2Echo.cs has an error that causes a compiler error.
Prior to the class definition should be the following statement:
using System;
Without this statement, the use of the Exception class is flagged by the
compiler.
|
Anonymous |
|
| Printed |
Page 73
The "snippet of C#" |
C = "A String";
should read:
C = "A string";
in order to be consistent with both figure 3-1 and the textual explanation just below
the snippet.
|
Anonymous |
|
| Printed |
Page 135
2nd paragraph |
This paragraph contains the text "of the most interest is verification of what you
wrote earlier". The words "what you wrote earlier" should be changed to something
along the lines of "what was mentioned previously".
|
Anonymous |
|
| Printed |
Page 142
Code listing in center of page |
Minor typo in the sample code description about overriding methods from base types
and interfaces
The code for class Type2 reads:
class Type2 : Type1, Type2 {
void Method3(){}
}
when it should read:
class Type2 : Type1, IFace2 {
void Method3(){}
}
This corresponds to the description in the second paragraph on page 143.
|
Anonymous |
|
| Printed |
Page 155
Figure 5-7 |
Figure 5-7 on page 155 appears to be incorrect based on what the accompanying text is
describing. This figure is an exact duplicate of Figure 5-8 on page 158, which does
appear to be the correct figure based on the subsequent text. Furthermore, the image
itself appears to have an error, the transformed stack on the right side shows two
identical labels of "int64 b" for the top two elements of the stack, but the top one
should likely be labeled as "int64 c".
|
Anonymous |
|
| Printed |
Page 155
Figure 5-7 |
Figure 5-7 on page 155, the diagram or illustration does not match the description of the figure. This figure is identical to Figure 5-8 on page 158. I think this illustration was mistakenly used for Figure 5-7 and (correctly) for Figure 5-8.
Figure 5-7 is supposed to show details for both x86 and PowerPC, but it does not. Instead, it shows a "before and after" transformation from the CLI stack to an x86 stack.
Where is the correct diagram for Figure 5-7?
|
Anonymous |
Feb 25, 2011 |
| Printed |
Page 160
1st paragraph |
This parapgraph references "opportunistic enregistering of top-of-stack that was
already mentioned", and I cannot find any previous paragraph that mentions
"opportunistic enregistering"
|
Anonymous |
|
| Printed |
Page 272
Figure 9-3 |
In figure 9-3, the words SEMIPROCESS (identifying the structure used in shared memory for process management)
should in fact be SHMPROCESS, discussed throughout the page surrounding the Figure.
|
Anonymous |
|
| Printed |
Page 311
CMI structures example |
In the lines that start "BYTE * pAllocState" and
"BYTE * protectionState", the comments on these lines should be
reversed and the "#endif //" should be moved to the following line.
The lines would then read:
BYTE * pAllocState; // Per-page allocation type tracking
BYTE * pProtectionState; // Per-page protection tracking
#endif // !HAVE_VM_ALLOCATE
|
Anonymous |
|