VS2005 和 Windows CE 6.0 调试 [英] VS2005 and Windows CE 6.0 Debugging
问题描述
首先，我运行的是 VS2005 SP1 和 Windows 7 Ultimate.
Firstly, I'm running VS2005 SP1 and Windows 7 Ultimate.
我正在尝试在运行 Windows CE 6.0 的设备上调试我的应用程序.
I'm trying to debug an application of mine on a device running Windows CE 6.0.
我已经做了很多挖掘，似乎很多人都有类似的困难，但它是由广泛的问题引起的，如果有任何解决方案，到目前为止他们都没有帮助我.
I have done a lot of digging and it seems a large amount people have a similar difficulty but it's caused by a broad range problems and if there are any solutions, none of them have helped me so far.
我的问题是我在调试时无法定位 WinCE 6.0.我能够定位的唯一设备是:
My problem is that I cannot target WinCE 6.0 when I debug. The only devices I am able to target are:
- Pocket PC 2003 设备
- Windows CE 5.0 设备
- Windows Mobile 5.0 掌上电脑设备
当我尝试简单地定位windows ce 5.0 设备"时，出现错误，例如:
When I attempt to simply target "windows ce 5.0 device" I get errors, for example:
Post-deploy error 0x00000001 returned after calling '\Windows\wceload.exe /noui \Windows\System_SR_enu.cab'. Device Connectivity Component
我找到了在 VS2005 和 WinCE 6.0 上构建应用程序的安装过程，我按照指南成功安装.过程如下，安装:
I have found installation processes for building application on VS2005 and WinCE 6.0 and I followed the guide with successful installations. The process was as follows, Install:
- VS2005
- VS2005 SP1
- MSDN(可选)
- WinCE 6.0
- WinCE 6.0 平台构建器 SP1
- WinCE 6.0 R2
- WinCE 6.0 R3
对可能的解决方案有什么想法吗?
Any idea on possible solutions?
谢谢
推荐答案
您是否安装了 CE 6.0 SDK?我认为那是你缺少的部分.您可以通过手动将指示的资源 CAB 复制到设备并在部署应用之前运行它来规避您在 5.0 目标中看到的错误.
Have you installed a CE 6.0 SDK? I think that's your missing piece. You can circumvent the error you're seeing with a 5.0 target by manually copying the indicated resource CAB to the device and running it before deploying your app.
编辑
一般来说，SDK 将来自设备 OEM.如果由于某种原因，您无法从 OEM 获得 SDK，那么您可以安装任何针对同一处理器的 SDK，并且它会起作用.请记住，SDK 可以过滤"出库和头文件，所以如果您有一个精简的 SDK，那么您可能没有一些您想要的头文件和库(尽管您始终可以动态加载您需要的功能).同样，如果目标设备没有您的 SDK 中的功能，您可能能够构建和链接不会在设备上运行的应用程序.如果设备具有通常随其 SDK 提供的自定义 API(用于 I/O 或其他)，那么如果您使用不同的 SDK，这些 API 也会丢失.不过，总比没有好.
The SDK, generally speaking, would come from the device OEM. If, for some reason, you can't get an SDK from the OEM then you can install any SDK targeting the same processor and it will work. Bear in mind that the SDK can "filter" out libs and headers, so if you have a trimmed-down SDK, then you may not have some of the headers and libs you want (though you can always dynamically load the functions you need). Likewise, if the target device doesn't have a feature that's in your SDK, you may be able to build and link and app that won't run on the device. If the device has custom API (for I/O or whatever) that typically comes with their SDK, then those would also be missing if you use a different SDK. Still, it's better than nothing.
我自己，我有一些为 x86 和 ARM 构建的 SDK，它们几乎没有厨房水槽.我只是在大多数设备开发中安装和使用这些 SDK.
Myself, I have a couple SDKs that I build for x86 and ARM that just have pretty much the kitchen sink thrown in. I just install and use those SDKs for most device development.
这篇关于VS2005 和 Windows CE 6.0 调试的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
