C# Column: Web Services, Remoting, and PocketPC

My most recent C# column has gone live on MSDN. In it, I talk about what I learned
in trying to build a remote control application that runs on the PocketPC using the
compact framework.


If you have comments on the column, please enter them, and I’ll be sure to respond.

Comments (4)

  1. Lau says:

    Thank you for a very good article. It is difficult to find good articles about this topic.
    I’m currently working on an application for a PocketPC and a server application. I need the server to invoke Internet Explorer when called from the PocketPC using System.Diagnostics.Process.Start(“http://www…”). I have followed your example and used the Web Service approach, but I keep getting an internal server error (“Remoting Exception”). It must be caused by some security problems on the server. How can I work around this problem? You suggest a lower level approach using sockets, but isn’t that going to cause the same problem?

  2. wpoust says:

    I’ve used both WebService and Remoting. To be honest, I like remoting better and we develop MS-based platforms but… I’m very concerned about will it be around 3-5 years from now. In trying to read between the lines, I am getting a message like "if you know what we know, you’d go web services". Kind of reminds me of the bush administration before the Iraq war. But where are the WMD?

  3. Bill says:

    In your article you mention that having to inherit from MarshalByRefObject is a bummer because it prevents one from being able to inherit from a custom base class. Would it be possible to define a custom base class (say, MyMarshalByRefObject) the inherits from MarshalBeRefObject and have the remoted class inherit this instead? Or is the remoted class restricted to only being able to inherit MarshalByRefObject.

    Also, you write that events are not supported on the .NET Compact Framework. Is it possible to use an asynchronous callback to work around this?

  4. MBA says:

    Helpful For MBA Fans.