Deleted the word 2005 after Visual Studio.

Changed this bullet to:

Windows XP with SP2 or higher, Windows Vista, Windows Server 2003
or Windows Server 2008 with IIS and MSMQ enabled

After Microsoft Visual Studio, changed the word 2005 to 2008.

Changed:
"This is preinstalled with Vista."
to
"This is installed with Visual Studio 2008."

Deleted the rest of this line from: "and .NET 3.0 Runtime Components (Windows SDK for .NET 3.0)"

Deleted the sixth bulleted item:

Deleted the word 2005 after Visual Studio.

Changed this bullet to:

Windows XP with SP2 or higher, Windows Vista, Windows Server 2003
or Windows Server 2008 with IIS and MSMQ enabled

After Microsoft Visual Studio, changed the word 2005 to 2008.

Changed:
"This is preinstalled with Vista."
to
"This is installed with Visual Studio 2008."

Deleted the rest of this line from: "and .NET 3.0 Runtime Components (Windows SDK for .NET 3.0)"

Deleted the sixth bulleted item.

The word 'principals' is used for 'principles.' There's another reported usage on pp 3.

Note from the Author or Editor:
This was fixed in August 2008 reprint.

Typo.

"with one anotehr to access"

Typo.

"with one anotehr to access"

Typo.

"addressing makes is possible"

is => it

Typo.

"addressing makes is possible"

is => it

Deleted this sentence: "Since you will be adding the WCF Service to an executable project (the
host) the template will also generate some code for hosting the service."

"Open IHelloIndigoService.cs and..." now reads "Open HelloIndigoService.cs and..."

"Open Program.cs and add code to host the new Main() entry point..." now reads "Open Program.cs and add code to the Main() entry point..."

Deleted this sentence: "Since you will be adding the WCF Service to an executable project (the
host) the template will also generate some code for hosting the service."

"Open IHelloIndigoService.cs and..." now reads "Open HelloIndigoService.cs and..."

"Open Program.cs and add code to host the new Main() entry point..." now reads "Open Program.cs and add code to the Main() entry point..."

The instructions seem to be really messed up:
====================
Rename Service1.cs and HelloIndigoService.cs and Service1.cs to IHelloIndigoService.cs and HelloIndigoService.cs, respectively.

I assmume that the following is what is intended:
====================
Rename IService1.cs and Service1.cs to IHelloIndigoService.cs and HelloIndigoService.cs, respectively.

Note from the Author or Editor:
Page 38, #2 reads:

"Rename Service1.cs and HelloIndigoService.cs and IService1.cs to IHelloIndigoService.cs and HelloIndigoService.cs, respectively."

A previous errata update was obviously poorly applied. It should read:

"Rename Service1.cs and IService1.cs to HelloIndigoService.cs and IHelloIndigoService.cs, respectively."

In the code block, "host=..." host is now in all lower case.

In the code block, "host=..." host is now in all lower case.

Right-click Reference.svcmap and select “Include in
Project.” Right-click localhost.map beneath Service Referenceslocalhost and select
“Exclude from Project.”

now reads:

Right-click serviceproxy.cs and select “Include in Project.” Right-click localhostReference.svcmap beneath
Service Referenceslocalhost and select “Exclude from Project.”

Right-click serviceproxy.cs and select “Include in
Project.” Right-click localhost.map beneath Service References and select
“Exclude from Project.”

now reads:

Right-click serviceproxy.cs and select “Include in Project.” Right-click localhostReference.svcmap beneath
Service Referenceslocalhost and select “Exclude from Project.”

Changed:
"localhost.map"
to:
"localhost"

Changed:
"localhost.cs"
to:
"Reference.cs"

Changed:
"localhost.map"
to:
"localhost"

Changed to:
"Now run the Host without debugging and generate a new proxy for WinClient."

Changed:
"and accepting localhost as the reference name"
to:
"and setting the namespace to localhost."

Changed:
"localhost.map"
to:
"localhost"

Changed:
"localhost.map"
to:
"localhost"

Changed:
"localhost.cs"
to:
"Reference.cs"

Changed:
"localhost.map"
to:
"localhost"

Changed to:
"Now run the Host without debugging and generate a new proxy for WinClient."

Changed:
"and accepting localhost as the reference name"
to:
"and setting the namespace to localhost."

Changed:
"localhost.map"
to:
"localhost"

Changed:
"introduce" incompatibilities
to:
"cause" incompatibilities

Changed:
"introduce" incompatibilities
to:
"cause" incompatibilities

Changed:
"run it once again."
to:
"run it without debugging."

Changed:
"run it once again."
to:
"run it without debugging."

Changed:
"the reference name"
to:
"the namespace"

Changed:
"the reference name"
to:
"the namespace"

Changed:
"ObservableCollection"
to:
"CollectionDataContract"

Changed:
"ObservableCollection"
to:
"CollectionDataContract"

After code block and before that paragraph inserted the following:

This behavior can also be set declaratively on the service type:

[ServiceBehavior(IgnoreExtensionDataObject=true)]

Chaned
"from being processed"
to
"from being processed at the service."

Changed:
"this feature"
to:
"IExtensibleDataObject"

After code block and before that paragraph inserted the following:

This behavior can also be set declaratively on the service type:

[ServiceBehavior(IgnoreExtensionDataObject=true)]

Chaned
"from being processed"
to
"from being processed at the service."

Changed:
"this feature"
to:
"IExtensibleDataObject"

Changed:
"reference name as localhost."
to:
"namespace as localhost."

Changed:
"reference name as localhost."
to:
"namespace as localhost."

Changed:
</SaveGigRequest>
to
</SaveGigResponse>

Changed:
</SaveGigRequest>
to
</SaveGigResponse>

Deleted the word "a" after "header is"

Deleted the word "a" after "header is"

In the last sentence in the third paragraph it says "...you can you serialize it...". The second "you"
was removed.

In the last sentence in the third paragraph it says "...you can you serialize it...". The second "you"
was removed.

Changed:
"reference name"
to:
"namespace"

Changed:
"reference name"
to:
"namespace"

Sentence two read:
"What is it missing is the configuration..."
and now reads:
"What it is missing is the configuration..."

Changed the last sentence to read:
"With Visual Studio 2008, Add Service Reference also supports this using Advanced options."

Changed the last sentence to read:
"With Visual Studio 2008, Add Service Reference also supports this using Advanced options."

Sentence two read:
"What is it missing is the configuration..."
and now reads:
"What it is missing is the configuration..."

Changed:
"they are ignored."
to:
"they are ignored when the contract is used as a callback contract."

Changed:
"they are ignored."
to:
"they are ignored when the contract is used as a callback contract."

Changed:
"reference name"
to:
"namespace"

"using System.Threading;"

Changed:
"reference name"
to:
"namespace"

"using System.Threading;"

Changed:
"subscriber"
to:
"callback"

IPublisherEvents callback = OperationContext.Current.GetCallbackChannel<IPublisherEvents>( );

Changed:
"callback"
to:
"id"

On lab step 2 in the second sentence there is a word "teh" which now reads "the".

Changed:
"subscriber"
to:
"callback"

IPublisherEvents callback = OperationContext.Current.GetCallbackChannel<IPublisherEvents>( );

Changed:
"callback"
to:
"id"

On lab step 2 in the second sentence there is a word "teh" which now reads "the".

Changed:
"fileUploadDir"
to:
"mediaPath"

Changed:
"fileUploadDir"
to:
"mediaPath"

Changed:
"reference as localhost"
to:
"namespace as localhost"

Changed:
"fileUploadDir"
to:
"mediaPath"

Changed:
"fileUploadDir"
to:
"mediaPath"

Changed:
"reference as localhost"
to:
"namespace as localhost"

Added the following to end of this paragraph:

Although a rare occurence, it is possible for the ServiceHost to be put into a faulted state. For example,
if there are errors in the service model configuration. If the ServiceHost State property is set to
CommunicationState.Faulted, when Close() is called an exception will be thrown. For this reason, it is best
to check the State property of the ServiceHost instance and call Abort() if it is in a faulted state. This
technique was illustrated in Chapter 1

Added the following to end of this paragraph:

Although a rare occurence, it is possible for the ServiceHost to be put into a faulted state. For example,
if there are errors in the service model configuration. If the ServiceHost State property is set to
CommunicationState.Faulted, when Close() is called an exception will be thrown. For this reason, it is best
to check the State property of the ServiceHost instance and call Abort() if it is in a faulted state. This
technique was illustrated in Chapter 1

Changed:
"reference name"
to:
"namespace"

Changed:
"reference name"
to:
"namespace"

Reads 1. Go to the WindowsServiceHost project...

Should be 1. Go to the MessagingServiceHost project...

Note from the Author or Editor:
In the August 2008 reprint, this error is on Page 267, step 2.

Change this: "Go to the WindowsServiceHost project..."

To this: "Go to the MessagingServiceHost project..."

Changed:
Windows "Longhorn" Server
to:
Windows Server 2008

After the word "deployments," deleted the rest of the paragraph starting with:
Thus, until Windows “Longhorn� Server is released, it has limited value...will pay off for Longhorn.

Changed:
Windows "Longhorn" Server
to:
Windows Server 2008

After the word "deployments," deleted the rest of the paragraph starting with:
Thus, until Windows “Longhorn� Server is released, it has limited value...will pay off for Longhorn.

Changed:
"Windows Longhorn Server"
to:
"Windows Server 2008"

Changed:
"Windows Longhorn Server"
to:
"Windows Server 2008"

Changed:
"Windows Longhorn Server"
to:
"Windows Server 2008"

Changed:
"Windows Longhorn Server"
to:
"Windows Server 2008"

Changed:
"Windows Longhorn Server"
to:
"Windows Server 2008"

Changed:
"Windows Longhorn Server"
to:
"Windows Server 2008"

Changed:
"Windows Longhorn Server"
to:
"Windows Server 2008"

Changed:
"Windows Longhorn Server"
to:
"Windows Server 2008"

Changed this section:
"also provide their own timeout...always be used for the session."
to:
"also have timeout properties but they do not control the timeout of the overall session. These properties
are described in later chapters."

Changed this section:
"also provide their own timeout...always be used for the session."
to:
"also have timeout properties but they do not control the timeout of the overall session. These properties
are described in later chapters."

Reads ...as shown in the Single instancing example of Figure 5-19.

Should be ...as shown in the Single instancing example of Figure 5-18.

Note from the Author or Editor:
This is correct in the August 2008 reprint.

"Although a new service instance is allocated for each request with PerCall services, Multiple concurrency
mode is still useful in the case where there is a session to increase throughput for multi-threaded clients.
That's because the lock acquired when the first request is received from a particular client proxy is
actually on the context, not on the service object. When a session is present, this lock prevents more than
one thread from entering the same session - which means the TCP socket, the named pipe, or the reliable or
secure session."

Changed:
"Figure 5-19"
to:
"Figure 5-18"

"Although a new service instance is allocated for each request with PerCall services, Multiple concurrency
mode is still useful in the case where there is a session to increase throughput for multi-threaded clients.
That's because the lock acquired when the first request is received from a particular client proxy is
actually on the context, not on the service object. When a session is present, this lock prevents more than
one thread from entering the same session - which means the TCP socket, the named pipe, or the reliable or
secure session."

Changed:
"Figure 5-19"
to:
"Figure 5-18"

Changed:
"2005"
to:
"2008"

Changed:
"2005"
to:
"2008"

Changed:
"serivce"
to:
"service"

Changed:
"serivce"
to:
"service"

"The release of the .NET Framework 3.5 includes a new feature for WCF - Durable Services. This feature makes
it possible to have an application session for a WCF service persist to a database between calls and be
restored on subsequent calls. This feature relies on the Windows Workflow Foundation persistence services.
This feature does not preserve transport sessions, so the client must still recreate the proxy if a
particular machine is no longer available, or if the session is terminated for some other reason."

"The release of the .NET Framework 3.5 includes a new feature for WCF - Durable Services. This feature makes
it possible to have an application session for a WCF service persist to a database between calls and be
restored on subsequent calls. This feature relies on the Windows Workflow Foundation persistence services.
This feature does not preserve transport sessions, so the client must still recreate the proxy if a
particular machine is no longer available, or if the session is terminated for some other reason."

Replaced paragraph with this:
"This is a TimeSpan property that controls the duration of the reliable session including channel layer
activity. If no messages, including infrastructure messages such as reliable session acknowledgements, are
transmitted during this elapsed time the session is faulted. The default value is 00:10:00 (or 10 minutes)."

Replaced paragraph with this:
"This is a TimeSpan property that controls the duration of the reliable session including channel layer
activity. If no messages, including infrastructure messages such as reliable session acknowledgements, are
transmitted during this elapsed time the session is faulted. The default value is 00:10:00 (or 10 minutes)."

Replaced code block with:

<wsHttpBinding>
<binding name="wsHttpRM" receiveTimeout="00:00:05">
<reliableSession enabled="true" ordered="true" />
</binding>
</wsHttpBinding>

Replaced code block with:

<wsHttpBinding>
<binding name="wsHttpRM" receiveTimeout="00:00:05">
<reliableSession enabled="true" ordered="true" />
</binding>
</wsHttpBinding>

Replaced first tip with:
"It simplifies matters greatly if you use the receive timeout setting to control session lifetime."

Replaced first tip with:
"It simplifies matters greatly if you use the receive timeout setting to control session lifetime."

Changed:
"Windows Longhorn Server"
to:
"Windows Server 2008"

Changed:
"Windows Longhorn Server"
to:
"Windows Server 2008"

Changed:
"Windows Longhorn Server"
to:
"Windows Server 2008"

Changed:
"Windows Longhorn Server"
to:
"Windows Server 2008"

Changed:
"Windows Longhorn Server"
to:
"Windows Server 2008"

Changed:
"Windows Longhorn Server"
to:
"Windows Server 2008"

Changed:
"DALC"
to
"Data Access"

Changed:
"DALC"
to
"Data Access"

Changed:
"DALC"
to
"Data Access"

Changed:
"DALC"
to
"Data Access"

Changed:
"reference name localhost."
to:
"namespace as localhost."

Changed:
"reference name localhost."
to:
"namespace as localhost."

Changed:
"DALC"
to
"Data Access"

Changed:
"DALC"
to
"Data Access"

Changed:
"DALC"
to
"Data Access"

Changed:
"DALC"
to
"Data Access"

Changed:
"2005"
to:
"2008"

Changed:
"2005"
to:
"2008"