用于 Windows Mobile WiFi 管理和控制的托管库/组件/API？
有谁知道我可以在 Windows Mobile 6 和 .NET CF 3.5 应用程序中使用的商业或免费 .NET CF 库/组件/API？
我需要：枚举范围内可用 WiFi 网络的列表，连接和断开列表中的特定 SSID/网络，并以编程方式管理 SSID 之间的切换（例如，我当前连接到“public1”并想要切换到“public2”做一些事情，然后切换回“public1”）。
我已经为此尝试了 OpenNETCF 库，它在某种程度上可以工作，但是它经常因本机异常而崩溃，我无法在 C# 代码中使用 catch() 来处理这种异常，因此它们会冒泡给最终用户，并得到一个令人讨厌的结果Windows 崩溃屏幕上有“发送”和“不发送”按钮。
OpenNETCF 论坛似乎已经死了，有很多帖子，但大多数都没有回复，而这些人的最后一次发布是在 2009 年 3 月。
Does anyone know of a commercial or free .NET CF library/component/api that I can use within my Windows Mobile 6 and .NET CF 3.5 application?
I need to: enumerate the list of available WiFi networks in range, connect and disconnect specific SSIDs/networks in the list, and manage switching between SSIDs programatically (e.g. I'm currently connected to "public1" and want to switch to "public2" to do some stuff, and then switch back to "public1").
I have tried the OpenNETCF library for this and it somewhat works, but it's crashing quite often with Native Exceptions, which I can't handle with a catch() in my C# code so they bubble up to the end user and they get a nasty windows crash screen with the "send" and "don't send" buttons.
OpenNETCF forums seem to be dead, with lots of posts but no replies to most of them, and the last release from those guys was way back in March 2009.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
最后我记得 OpenNETCF 代码很不错，并且在我尝试过的许多设备上都没有任何问题。我当然不记得从中得到本机异常。
您有可能在定制平台上工作吗？真正的问题可能是由于对您的特定设备/操作系统所做的修改造成的。
IIRC 由于硬件或成本原因，我们最终改用 Summit 卡，它使用不同的 API，但显然该 API 只能与 Summit 卡一起使用。
恐怕我不知道还有其他替代自动取款机。对不起。 :(
Last I remember the OpenNETCF code was decent and worked without any issues on a number of devices I tried it on. I certainly don't remember getting native exceptions from it.
Is it possible that you're working on a customised platform? It is possible that the real issue might be due to modifications made to your particular device / operating system.
IIRC we eventually switched to Summit cards for hardware or cost reasons which uses a different API but obviously an API that would only work with Summit cards.
I'm afraid I don't know of any other alternatives atm. Sorry. :(