Errata

Programming .NET Components

Errata for Programming .NET Components

Submit your own errata for this product.

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 44
Inbetween 2nd and 3rd paragraph

The books states:

"However, the same client will function just fine (without recompiling) if you change the order of the methods in the interface:

public interface IMyInterface
{
void Method2();
void Method1();
}

or if you add a new method:

public interface IMyInterface
{
void Method3();
void Method1();
void Method2();
}
"

The client will NOT work fine if a new "void Method3()" is added since the runtime will throw an exception complaining that the client didn't implement the new "Method3". .Net Interfaces are IMMUTABLE! The only change that I see possible is reordering the methods

Anonymous   
Printed Page 55
Example 3-6 Using the as operator to cast

The following line in the if-clause:

obj.Method1();

from the context, it should be:
obj1.Method1();

Anonymous   
Printed Page 94
3rd paragraph

When the object does not implement IDisposable, the compiler refuses to compile the code, claiming the object should be implicitly convertible to IDisposable. Therefore, a "using" statement can only be used with types which implement the IDisposable interface.

Anonymous  Oct 28, 2010 
Printed Page 99

Template for deterministic finalization does not distinguish between Cleanup() called from finalizer and Cleanup() called from Dispose(). Cleanup() implementation therefor can't safely access or dispose member variables, it can only release unmanaged resources. This limitation is not made clear in the text.

Anonymous  Sep 13, 2010 
Printed Page 104
4rd; In the Versioning chapter.

I tried to put the * char in the assembly information form but it told that the wildcard is not alowed. But I still can change it in the assemblyinfo.cs.

Im sure is a vs failure for not allowing the * char, if I put the char in the assemblyinfo.cs as i said when I open the information form later I get that the * is there...

Anonymous   
Printed Page 351
2nd paragraph

The available formatters are SoapClientFormatterSinkProvider and
BinaryClientFormatterSinkProvider, implementing the IClientChannelSinkProvider interface.

should read

The available formatters for the client are SoapClientFormatterSinkProvider and
BinaryClientFormatterSinkProvider, implementing the IClientChannelSinkProvider interface.

Anonymous