Deploying Pocket PC Applications

Article
07/05/2006

After developing a speech-enabled Web application for use on Pocket PC clients, deploy the application on a Web server and test it.

To deploy a speech-enabled Web application for access from Pocket Internet Explorer:

Ensure that application files that contain SALT markup map file extensions to MIME types. For .asp and .aspx pages, set the MIME type in code. For all other file types, use file-type mapping as described in the following section. This causes the Microsoft Speech Add-in for Microsoft Pocket Internet Explorer to automatically instantiate SALT objects. The correct MIME type settings are listed in the following table.

File Type MIME Type

.htm/.html files text/salt+html

.grxml/.ssml files text/xml
Using Internet Information Services (IIS), set the directory containing the speech-enabled Web application as an application root directory.
Install the Speech Add-in for Microsoft Pocket Internet Explorer on each Pocket PC client that will be used for testing the application. For more information, see the topic entitled "Installing the Speech Add-ins" in the Microsoft Speech Server 2004 (MSS) Help documentation on the MSS CD.

File Type	MIME Type
.htm/.html files	text/salt+html
.grxml/.ssml files	text/xml

Any Pocket PC with the Speech Add-in for Microsoft Pocket Internet Explorer installed can run the speech-enabled Web application by opening the URL of the Web application's main page.

Setting the MIME Type for .asp and .aspx Pages

To set the MIME type for .aspx pages, in the code-behind page use the ContentType property of the Response object as in the following example.

private void Page_Load(object sender, System.EventArgs e)
            { 
                  //code to initialize the page...
                  Response.ContentType = "text/salt+html";
            }

To set the MIME type for .asp pages, in server-side ASP script use the ContentType property of the Response object as in the following example.

<% Response.ContentType = "text/salt+html" %>

Mapping File Extensions to MIME Types

To map file extensions to MIME types on Windows Server 2003

In Control Panel, double-click Administrative Tools, and then double-click Internet Information Services (IIS) Manager.
In IIS Manager, expand the tree view in the left-hand pane.
In the tree view pane on the left, under the Web Sites folder, right-click the directory containing the Web project and select Properties.
On the properties dialog box, click the HTTP Headers tab, and then in the MIME Types panel click the MIME Types... button.
On the MIME Types dialog box, click New....
On the MIME Type dialog box, in the Extension field, type a period followed by the three-letter extension for one of the file types that require the Speech Add-in (for example, .grxml, .htm).
In the MIME type field, type the MIME type for that extension.
Click OK to save all changes.

To map file extensions to MIME types on Windows XP

In Control Panel, double-click Administrative Tools, and then double-click Internet Information Services.
Expand the tree view in the left-hand pane, and locate the directory containing the Web project. Right-click the Web project directory and in the context menu, click Properties.
On the HTTP Headers tab in the MIME Map pane, click File Types....
On the File Types dialog box, click New Type....
On the File Type dialog box, in the Associated extension field, type a period followed by the three-letter extension for one of the file types that require the Speech Add-in (for example, .grxml, .htm)
In the Content type (MIME) field, type the MIME type for that extension.
Click OK to save all changes.

Checking for Client Installation

To verify that a client is installed, each page should check that the Accept HTTP header includes the value "text/salt+html". If this check fails, then the application should send a page explaining that the user needs to install client software, with a link to an installation source. For more information on Accept headers, see the topic HTTP Headers Reference in Visual Studio .NET 2003 Help.

Partager via