 | ||
|
| ||
| ||
|
| ||
Preview Release (see note)
July 13, 1998
Contents
Subscribing to a Local CDF File
Subscribing to a Remote CDF File
Synchronizing Files
Broken Links
Debugging Scripts
Resubscribing to Channels
By using the powerful, new Mobile Channels technology, you can provide dynamic HTML content to mobile devices. However, it is inevitable for developers to run into unknown challenges when learning a new technology. The following hypothetical situations reflect common problems and their solutions.
While developing a mobile channel, you choose to design and debug a CDF file on a local machine. However, Internet Explorer 4.0 does not let you subscribe to that CDF file, and you are unable to update your content.
Cause
Internet Explorer 4.0 is not designed to access local CDF files.
Resolution
Upload your CDF file to a Web server.
After posting your CDF file to a Web server, you are unable to access it through Internet Explorer 4.0.
Cause
Your CDF file may have syntax errors.
Resolution
Check that all your tags have proper quoting and closure, and use Xmlint.exe to verify your CDF file before uploading it to the server. For more information about XMLint, see Mobile Channels Resources.
Images synchronize to the Temporary Internet Files folder on your desktop computer, but do not appear in Internet Explorer 4.0 or the Channel Browser.
Cause
The Channel Browser cannot resolve relative HREFs for images.
Resolution
Use absolute image HREFs when designing your pages.
Your channel works correctly when displayed by Internet Explorer 4.0, but some of the links and images appear broken on your Windows CE-based target device.
Cause
Internet Explorer 4.0 can access the images and pages regardless of their status in your channel's CDF file. However, your target device only downloads pages and images specified in your CDF file.
Resolution
Be sure that your CDF file contains all the correct image and page references.
You want to debug your script using an effective tool.
Resolution
Use a debugger such as DBWin32 and place MC.Debug statements at strategic points in your script. For more information about DBWin32, see Mobile Channels Resources. For more information about MC.Debug, see Mobile Channels Scripting Reference.
You test your content update procedures by deleting and resubscribing to your mobile channel. However, the system does not properly route you through the download sequence.
Cause
If you choose to delete and resubscribe to the same channel, Mobile Channels does not properly clean up the channel until you subscribe to another mobile channel first.
Resolution
The recommended way to test content updates is to right-click the mobile channel in the Channel Bar in Internet Explorer 4.0 and choose Update Now. If you must delete and resubscribe to your mobile channel, subscribe to a different mobile channel first, thus forcing Mobile Channels to perform cleanup. Resubscribing to your original mobile channel then initiates the expected download sequence.
Did you find this material useful? Gripes? Compliments? Suggestions for other articles? Write us!
© 1999 Microsoft Corporation. All rights reserved. Terms of use.
Back to top