Select the product you need help with
MCTS Self-Paced Training Kit (Exam 70-529): Microsoft .NET Framework 2.0 Distributed Application Development Comments and CorrectionsArticle ID: 930423 - View products that this article applies to. On This PageSUMMARY
This article contains comments, corrections, and information about known errors relating to the Microsoft Press book MCTS Self-Paced Training Kit (Exam 70-529): Microsoft .NET Framework 2.0 Distributed Application Development, 978-0-7356-2332-3. The following topics are covered:
MORE INFORMATIONCDROM: Some references contain broken linksIn 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
(http://msdn2.microsoft.com/en-us/library/aa302407.aspx)
Understanding enterprise Services (COM+) in .NET http://msdn2.microsoft.com/en-us/library/ms973847.aspx
(http://msdn2.microsoft.com/en-us/library/ms973847.aspx)
Page 28: "ws WebService" should be "WebService ws"On page 28, the first line of the C# code sample is incorrect.Change: To: Page 57: Header element example missing closing tagOn page 57, the Header element example at the top of the page is missing a closing tag for <soap12:Header>Add the following line after </soap12:Body>: Page 95: C# code example is partially incorrectOn page 95, the third line down in the C# example is incorrect.Change: To: Page 98: C# code example missing charactersOn page 98, the 9th line in the C# code sample is partially incorrect and a new line needs to be added before it.Change: To: Page 174: "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." Page 175: "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." Page 190: instructions for Step 7 are partially incorrectOn 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:" Page 191: console output is incorrectOn page 191, the output under Step 9 is partially incorrect.Change: To: Page 291: 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."" Page 292: "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." Page 312: Instructions incorrect regarding adding referencesOn 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." Page 314: Incorrect reference in Step 17On 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.)" Pages 315 and 316: Namespace missing from sample codeOn 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: On page 316, add the following line to the beginning of the C# code: Page 357: Incorrect image used in Figure 9-1On 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.Page 357: Incorrect image used in Figure 9-2On 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.Page 366: Incorrect image used in Figure 9-4On page 366, the image used in Figure 9-4 is incorrect and should be disregarded.Page 374: Incorrect image used in Figure 9-5On page 374, the image used in Figure 9-5 is incorrect and should be disregarded.Page 374: Incorrect image used in Figure 9-6On page 374, the image used in Figure 9-6 is incorrect and should be disregarded.Page 377: Incorrect image used in Figure 9-7On 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.Page 438: Incorrect namespace used in codeOn 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. Properties |


Back to the top








