.NET 中的 IRAPIStream COM 接口
我正在尝试使用 OpenNETCF RAPI 类通过 RAPI.Invoke() 方法与 Windows 移动设备进行交互。
根据以下文章: http://blog.opennetcf.com/ncowburn/2007/07/ 27/HOWTORetrieveTheDeviceIDFromTheDesktop.aspx
您可以以块或流模式进行通信。 我以前使用过块模式,但现在我需要做一些更复杂的事情,需要更多的数据和连续的通信,因此需要使用流模式。 不幸的是,在那篇文章中,以及基本上其他地方,没有解释如何在 .NET 中使用 IRAPIStream 我找到了 C/C++ 文档,但我的桌面应用程序需要用 C# 编写
有谁知道如何在.NET中正确实现IRAPIStream COM接口? 更好的是,以前有人真正将 RAPI.Invoke() 与 IRAPIStream 一起使用过吗? 例子将非常感激。
编辑:仔细查看 RAPI 类文档后,我意识到 Invoke() 方法不支持流接口......所以 OpenNETCF 可能已经退出,但也许还有办法做到这一点?
I'm trying to use the OpenNETCF RAPI class to interact with a windows mobile device using the RAPI.Invoke() method.
According to the following article:
http://blog.opennetcf.com/ncowburn/2007/07/27/HOWTORetrieveTheDeviceIDFromTheDesktop.aspx
You can do the communication in either block or stream mode. I have used block mode before, but now I need to do something a bit more complicated with a lot more data and continuous communication and therefore need to use the stream mode. Unfortunately on that article, and basically everywhere else, there is no explaination of how to use IRAPIStream in .NET I have found C/C++ documentation, but my desktop app needs to be written in C#
Does anyone know how to properly implement the IRAPIStream COM interface in .NET?
And better yet, anyone actually used RAPI.Invoke() with IRAPIStream before? Examples would be much appreciated.
Edit: Upon a closer look at the RAPI class documentation, I realized that the Invoke() method doesn't support the stream interface.... so OpenNETCF is likely out, but maybe there is still a way to do it?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
我发现通常通过 activesync 推送/拉取设备大量数据的最高效、最稳定的方法是使用套接字。
早期,我们使用 CeRapiInvoke 和流来从设备中提取数据,但早期放弃了这一点,转而通过套接字使用 tcp/ip。
I have found that generally the most performant and stable way to push/pull large amounts of data of a device over activesync is to use a socket.
Early on we used CeRapiInvoke and a stream to pull data down of the device but ditched this early on in favour of using tcp/ip over a socket.