longshine
commented
9 years ago Hi,
Sorry that we haven't run CoAP.NET on .NET CF yet. I think these following points might be the reasons that make your app stop working:
- Use of System.Timers.Timer, which is said not being supported in .NET CF.
- Dependency on Remoting. An internal HTTP server of CoAP.NET is built on .NET Remoting, which is neither supported. See http://msdn.microsoft.com/en-us/library/2weec7k5%28v=vs.90%29.aspx.
- The required Common.Logging library is not built for .NET CF.
As for a solution, you may try these steps:
- Replace System.Timers.Timer with System.Windows.Forms.Timer (suggested in MSDN)
- Remove the dependency on System.Runtime.Remoting, implement a new CoAP.HTTP.WebServer, or just remove the whole CoAP.Proxy and CoAP.HTTP namespace, . It won't affect the functionality of CoAP protocol.
- Rebuild Common.Logging, targeting .NET CF, or remove it.
However, I'm not quite sure it will work or not. You may try the CoAPSharp (http://www.coapsharp.com/) lib for alternative.
I was planning to run this library in windows mobile 6.1 with compact net framework 3.5, however I could not run in the mobile emulator , It requires libraries from compact .net Framework 4.0.
Does CoAP.NET supports .NET compact framework 3.5