Win Mobile 5.0 无法调试和用户 WiFi
我有一个必须调试的应用程序。它是 Windows Mobile 5.0 上的 C++，并通过 WiFi 使用网络连接。 （Visual Studio 2008。）
从 USB 断开并主动同步后，应用程序可以正常连接到网络，但是一旦我将其插入底座（并因此通过 ActiveSync 连接），它就会自动禁用 WiFi 网络，我可以'无论如何似乎找不到重新打开它。
我需要 ActiveSync 来控制调试器中的程序，并且需要 WiFi 来运行应用程序，但我似乎只能选择其中之一。
有人有什么想法吗？请让我不必通过 printf 语句进行调试:-)
I have an app that I have to debug. It is C++ on Windows Mobile 5.0, and it uses a network connection via WiFi. (Visual Studio 2008.)
Disconnected from USB and active sync the app connects to the network just fine, but as soon as I plug it into the cradle, (and consequently connect via ActiveSync) it automatically disables the WiFi network, and I can't seem to find anyway to turn it back on.
I need ActiveSync to control the program in the debugger, and I need WiFi to have the application run, but I seem to only be able to have one or the other.
Does anyone have any ideas? Please save me from having to resort to debugging via printf statements :-)
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
不要使用 ActiveSync - 直接通过 WiFi 连接进行调试< /a>.
Don't use ActiveSync - debug directly through the WiFi connection.
我最近通过 WiFi 进行了可靠的财富调试。神奇之处似乎在于配置设备的传输 IP 地址并使用 ActiveSync 来启动该过程。
（我在 Windows 7 (x64) 系统上使用 Visual Studio 2008；以及 Windows Mobile 6.5 设备，以防万一。）
开始将下面列出的五个文件复制到移动设备。
如果幸运的话，应用程序将启动，就像它仍然连接到 ActiveSync 一样。您甚至可以编译和部署更新的文件，而无需重新连接 ActiveSync。
第一次这个方法奏效时，我想我的下巴都撞到了地上；我偶然发现了它，简直不敢相信它能起作用。
[在没有 ActiveSync 的 CE5.0 设备上调试] 针对 Visual Studio 2005 beta2 讨论了这一点；这似乎是相关的。 （此问题的另一个答案中也引用了此链接）。
这些说明包括将 5 个文件从主机
\Program Files\Common Files\Microsoft Shared\CoreCon\1.0\Target\wce400\复制到设备上的\windows。我将 5 个文件从
\Program Files (x86)\Common Files\Microsoft Shared\CoreCon\1.0\Target\wce400\armv4复制到设备上的\VSDebugFiles（预计对它们进行实验）。我发现，如果 Visual Studio 拒绝按照上述步骤进行连接，则在设备上运行 CMAccept 会有所帮助。万一链接被删除，这五个文件是：
好吧，我承认这仍然是非常偶然的，但它经常发生。
如果您没有方便的方法来检查设备的 IP，请尝试 VxUtil；它是我验证 Windows Mobile 网络连接的首选网络实用程序。
祝你好运，希望它有效。
I've recently been having reliable fortune debugging over WiFi. The magic seems to be configuring the device's transport IP address and using ActiveSync to jump-start the process.
(I'm using Visual Studio 2008 on a Windows 7 (x64) system; and a Windows Mobile 6.5 device, in case it matters.)
Start up copying the five files listed below unto the mobile device.
With any luck, the app will start just as if it were still connected to ActiveSync. You can even compile and deploy updated files without needing to reconnect ActiveSync.
First time this worked, I think my jaw hit the ground; I stumbled upon it by chance and simply couldn't believe it was working.
[Debugging on CE5.0 device without ActiveSync] discusses this for Visual Studio 2005 beta2; it seems to be relevant. (This link is also cited in another answer to this question).
The instructions include copying 5 files from host
\Program Files\Common Files\Microsoft Shared\CoreCon\1.0\Target\wce400\<CPU>to\windowson the device.I copied the 5 files from
\Program Files (x86)\Common Files\Microsoft Shared\CoreCon\1.0\Target\wce400\armv4to\VSDebugFileson my device (expecting to experiment with them). What I did find was that, if Visual Studio refused to connect following the above steps, runningCMAccepton the device would help.In case the link is ever removed, the five files are:
Ok, I admit that this is still very hit or miss, but it is hitting more often than not.
If you don't have a convenient way to check your device's IP, try VxUtil; it's my go-to network utility for validating Windows Mobile network connections.
Good luck, hope it works.