Article ID: 908274 - Last Review: May 10, 2006 - Revision: 1.0

Debugging fails, and you do not receive a clear error message about the failure in Visual Studio 2005

View products that this article applies to.

System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.

Expand all | Collapse all

SYMPTOMS

Consider the following scenario. You try to debug an application by using Microsoft Visual Studio 2005. The application is built for a Microsoft Windows Mobile 5.0-based Pocket PC. In this scenario, the application does not run on the device, and debugging fails. Additionally, you do not receive a clear error message about the failure in Visual Studio 2005.

Typically, this problem occurs after you change the deployment target in Visual Studio 2005 to the Pocket PC 2003 emulator.

Back to the top

CAUSE

This problem occurs because the Visual Studio debugger cannot process error messages correctly when you try to run the application by using an incompatible CPU type. The Pocket PC 2003 emulator is incompatible with a Windows Mobile 5.0-based Pocket PC.

Back to the top

WORKAROUND

To work around this problem, change the deployment target to the Windows Mobile 5.0 Pocket PC Software Development Kit (SDK). To do this, follow these steps:

Start Visual Studio 2005.
On the Project menu, click Change Target Platform.
In the Change Target Platform dialog box, click Windows Mobile 5.0 Pocket PC SDK under Change to, and then click OK.

Back to the top

MORE INFORMATION

For more information about how to debug a Windows Mobile 5.0-based application in Visual Studio 2005, visit the following Microsoft Developer Network (MSDN) Web site:

http://msdn.microsoft.com/mobility/ (http://msdn.microsoft.com/mobility/)

Back to the top