Errata for Microsoft® Mobile Development Handbook

Visual Studio 2007 should be Visual Studio 2008 On page 5, the 7th sentence in the first paragraph refers to an incorrect version of Visual Studio. Change: "The version of the desktop .NET Framework that ships with Microsoft Visual Studio 2007 is 3.5, and the version of the .NET Compact Framework that ships with Visual Studio 2007 is also 3.5." To: "The version of the desktop .NET Framework that ships with Microsoft Visual Studio 2008 is 3.5, and the version of the .NET Compact Framework that ships with Visual Studio 2008 is also 3.5."

Windows Mobile 6.0 should be Windows Mobile 6 On page 7, the first sentence of the first paragraph contains an incorrect version number for Windows Mobile. Change: "If you want to develop applications for Windows Mobile 6.0–powered devices, download a Windows Mobile 6.0 SDK that contains documentation, tools, and new emulators that run Windows Mobile 6.0 that you can use during development." To: "If you want to develop applications for Windows Mobile 6–powered devices, download a Windows Mobile 6 SDK that contains documentation, tools, and new emulators that run Windows Mobile 6 that you can use during development."

Incorrect reference to Chapter 16 On page 14, the last sentence of the first paragraph of the "Programming API Differences" contains an incorrect reference to chapter 16 and should be removed. The sentence currently reads: "See Chapter 16, “The Windows Mobile 5 Managed APIs,” for more detail on these libraries."

Video Graphics Adapter should be Video Graphics Array On page 29, the third sentence in the first paragraph under the "Screen Resolution Handling" heading contains an incorrect definition for VGA. Change: "If you have developed a UI for a Quarter VGA (QVGA) display, what will it look like on a Video Graphics Adapter (VGA) display?" To: "If you have developed a UI for a Quarter VGA (QVGA) display, what will it look like on a Video Graphics Array (VGA) display?"

ResolutionAwareControl should be OrientationAwareControl On page 66, the last line of Step 2 refers to a ResolutionAwareControl rather than an OrientationAwareControl. Change: "ResolutionAwareControl as follows:" To: "OrientationAwareControl as follows:"

Incorrect } placement in code sample On page 99, a } is in the incorrect location in the first code sample, excluding the Dispose method from the class. Change: } public new void Dispose() { if (this.Connection != null) { this.Connection.Dispose(); } base.Dispose(); } }To: public new void Dispose() { if (this.Connection != null) { this.Connection.Dispose(); } base.Dispose(); } } }

conn missing from code sample On page 106, the third line of the second code sample is missing a prameter for the ProductsCategoryResultSet method. Change: new JoinQueryResultSetResultSets.ProductsCategoryResultSet(false);To: new JoinQueryResultSetResultSets.ProductsCategoryResultSet(false, conn);

Incorrect placement of } and formatting in code sample On page 172, there is a } included in the wrong place, and inconsistant formatting in the code sample. Change: }else{ // TODO handle other status values } catch (Exception ex2) { Debug.WriteLine(ex2.Message); } }To: } else { // TODO handle other status values } } catch (Exception ex2) { Debug.WriteLine(ex2.Message); }

"seconds" should be "milliseconds" On page 214, the first line in the code sample at the bottom of the page contains an incorrect unit of measurement. Change: // Takes ~ 5 minutes (i.e., 300,000 seconds)To: // Takes ~ 5 minutes (i.e., 300,000 milliseconds)

ShowTopic should be ShowHelp On page 225, the second paragraph and following code sample reference ShowTopic rather than ShowHelp. Change: "To start a help topic in your application, you can use the Process class in the System.Diagnostics namespace to start the .htm file. The following ShowTopic method is designed to behave much like the System.Windows.Forms.Help.ShowTopic method, which is not available on smartphones. You should pass in the full path of an HTML file containing your help content." public static void ShowTopic(string url) { Process.Start(url, ""); }To: "To start a help topic in your application, you can use the Process class in the System.Diagnostics namespace to start the .htm file. The following ShowHelp method is designed to behave much like the System.Windows.Forms.Help.ShowHelp method, which is not available on smartphones. You should pass in the full path of an HTML file containing your help content." public static void ShowHelp(string url) { Process.Start(url, ""); }

Next should be OK On page 255, the second paragraph uses Next in place of OK. Change: "In the Guidance Package Manager, click the Enable/Disable Packages button, and on the next screen, select Mobile Client Software Factory, as shown in Figure 7-3, and then click Next." To: "In the Guidance Package Manager, click the Enable/Disable Packages button, and on the next screen, select Mobile Client Software Factory, as shown in Figure 7-3, and then click OK."

Services should be Server On page 269, the first sentence refers to Microsoft Transaction Services rather than Microsoft Transaction Server. Change: "The .NET Compact Framework doesn’t support distributed transactions (such as those that can be achieved using SQL Server Distributed Transaction Coordinator [DTC], Microsoft Transaction Services [MTS], or COM+ components) across databases or servers." To: "The .NET Compact Framework doesn’t support distributed transactions (such as those that can be achieved using SQL Server Distributed Transaction Coordinator [DTC], Microsoft Transaction Server [MTS], or COM+ components) across databases or servers."

Enterprise Manager should be Management Studio On page 283, the first sentence of the second paragraph makes reference to Enterprise Manager rather than Management Studio. Change: "To complete the security setup in the database, run the SQL Server Enterprise Manager and locate the sample database called Traffic." To: "To complete the security setup in the database, run the SQL Server Management Studio and locate the sample database called Traffic."

OLEDBConnection String should be OLEDBConnectionString and OLDB should be OLEDB On page 286, the third row of Table 7-4 contains two errors. Change: "OLEDBConnection String" To: "OLEDBConnectionString" Change: "The OLDB connection string for the SQL Server database." To: "The OLEDB connection string for the SQL Server database."

Semicolon missing from code sample On page 476, the second code sample is missing a semicolon. Change: float aspectRatio = ((float)device.PresentationParameters.BackBufferWidth) / device.PresentationParameters.BackBufferHeightTo: float aspectRatio = ((float)device.PresentationParameters.BackBufferWidth) / device.PresentationParameters.BackBufferHeight;

References to a diagram should be removed On page 481, the paragraph following Figure 13-5 contains references to a missing diagram. Change: "The origin of the texel coordinates is 0,0. The texel value can range up to 1.0 in either direction, The diagram shows how the texture is broken into triangles. The code to create the vertices for these triangles is as follows:" To: "The origin of the texel coordinates is 0,0. The texel value can range up to 1.0 in either direction. The code to create vertices for breaking the texture into two triangles is as follows:"

distributed should be digital On page 581, the third sentence uses the phrase "distributed rights management" rather than "digital rights management". Change: "You can toggle whether distributed rights management (DRM) content is displayed to the user." To: "You can toggle whether digital rights management (DRM) content is displayed to the user."

2005 should be 5.0 On page 590, the first sentence refers to "Microsoft Windows Mobile 2005" rather than "Microsoft Windows Mobile 5.0". Change: "The new version of the .NET Compact Framework runtime is supported on exactly the same platforms as v2.0: Pocket PC 2003 and later, smartphones running Microsoft Windows Mobile 2005 and later, and embedded hardware running Windows CE 4.2 and later." To: "The new version of the .NET Compact Framework runtime is supported on exactly the same platforms as v2.0: Pocket PC 2003 and later, smartphones running Microsoft Windows Mobile 5.0 and later, and embedded hardware running Windows CE 4.2 and later." 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.