Errata for MCTS Self-Paced Training Kit (Exam 70-529): Microsoft® .NET Framework 2.0 Distributed Application Development

Some references contain broken links In the Readiness Review Assessment there are several practice test questions which contain references with broken links to external websites. The following are 2 broken links used in the References section of several Readiness Review Assessment questions. Building Secure ASP.NET applications Authentication, Authorization, and Secure Communication http://msdn2.microsoft.com/en-us/library/aa302407.aspx Understanding enterprise Services (COM+) in .NET http://msdn2.microsoft.com/en-us/library/ms973847.aspx

"ws WebService" should be "WebService ws" On page 28, the first line of the C# code sample is incorrect. Change: ws WebService = new WebService.Service(); To: WebService ws = new WebService.Service();

Header element example missing closing tag On page 57, the Header element example at the top of the page is missing a closing tag for Add the following line after :

C# code example is partially incorrect On page 95, the third line down in the C# example is incorrect. Change: if (Session["UserID"] != null)To: if (Session["UserID"] == null)

C# code example missing characters On page 98, the 9th line in the C# code sample is partially incorrect and a new line needs to be added before it. Change: cookie = new System.Net.CookieContainer;To: Session.Add("CookieJar", cookie); cookie = new System.Net.CookieContainer();

"TcpServerChannel" should be "TcpClientChannel" On page 174, the 2nd and 3rd sentence of the first paragraph on the page incorrect references the wrong class. Change: "The TCP channel is instantiated using the System.Runtime.Remoting.Channels.Tcp.TcpServerChannel class. The TcpServerChannel class can be configured to transport messages into either binary format or SOAP format." To: "The TCP channel is instantiated using the System.Runtime.Remoting.Channels.Tcp.TcpClientChannel class. The TcpClientChannel class can be configured to transport messages into either binary format or SOAP format."

"IpcServerChannel" should be "IpcClientChannel" On page 175, the 1st and 2nd sentence in the second paragraph on the page references the wrong class. Change: "The IPC channel is instantiated using the System.Runtime.Remoting.Channels.Ipc.IpcServerChannel class. The IpcServerChannel class can be configured to transport messages into either binary format or SOAP format." To: "The IPC channel is instantiated using the System.Runtime.Remoting.Channels.Ipc.IpcClientChannel class. The IpcClientChannel class can be configured to transport messages into either binary format or SOAP format."

instructions for Step 7 are partially incorrect On page 190, Step 7 incorrectly states that the code needs to be placed below the channel registration. Change: "7. Below the channel registration, type the following code to create an instance of the remote Patient type:" To: "7. Below the Remote Patient Object registration, type the following code to create an instance of the remote Patient type:"

console output is incorrect On page 191, the output under Step 9 is partially incorrect. Change: Patient ID: 001 :: John Doe :: 123 Main Street :: Someplace, AZ 85000 01/12/2001; Diagnosis: cold | Treatment: take 2 and call me in the morning. 03/04/2005; Diagnosis: broken toe | Treatment: nothing.To: Patient ID: 001 :: Demo Patient 01/12/2001; Diagnosis: cold | Treatment: take 2 and call me in the morning. 03/04/2005; Diagnosis: broken toe | Treatment: nothing.

Microsoft should be "Method completed: System.Object Value: Microsoft" On page 291, the last sentence of step 3 is incorrect. Change: "Run the application and you should see the words I’m running async output to the console window followed by the word Microsoft." To: "Run the application and you should see the words I’m running async output to the console window followed by "Method completed: System.Object Value: Microsoft.""

"Microsoft" should be "I made it so the OneWay attribute worked!" On page 292, the last sentence of Step 11 is incorrect. Change: "Run the application and you should see the word Microsoft in the console window." To: "Run the application and you should see "I made it so the OneWay attribute worked!" in the console window."

Instructions incorrect regarding adding references On page 312, the third sentence of Step 10 is incorrect and needs to be reversed. Change: "Repeat this process to add a reference in the StandardInterfaces project to the StandardServer project." To: "Repeat this process to add a reference in the StandardServer project to the StandardInterfaces project."

Incorrect reference in Step 17 On page 314, the fourth sentence in Step 17 references an incorrect previous step. Change: "(This project should already have a reference to the StandardInterfaces project, which you added in step 9.)" To: "(This project should already have a reference to the StandardInterfaces project, which you added in step 10.)"

Namespace missing from sample code On pages 315 and 316, in Step 18 the namespace required for the Activator class is missing from both the VB and C# code sample. On page 315, add the following line to the beginning of the VB code: Imports SystemOn page 316, add the following line to the beginning of the C# code: using System;

Incorrect image used in Figure 9-2 On page 357, the image used in Figure 9-2 is incorrect and should be replaced with the image used in Figure 9-6 on page 374.

Incorrect image used in Figure 9-1 On page 357, the image used in Figure 9-1 is incorrect and should be replaced with the image used in Figure 9-5 on page 374.

Incorrect image used in Figure 9-4 On page 366, the image used in Figure 9-4 is incorrect and should be disregarded.

Incorrect image used in Figure 9-5 On page 374, the image used in Figure 9-5 is incorrect and should be disregarded.

Incorrect image used in Figure 9-6 On page 374, the image used in Figure 9-6 is incorrect and should be disregarded.

Incorrect image used in Figure 9-7 On page 377, the image used in Figure 9-7 is incorrect and should be replaced with the image used in Figure 9-1 on page 357.

Incorrect namespace used in code On page 438, the first line of code in Step 13 uses an incorrect namespace. Change: To: 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.