Re: Using COM OutProc server on WinCE

Thanks for the useful reply. My original XP application that I want to
port on CE and WM5 is a wireless application (like MS Windows Zero Config)
and I am having myUI.exe that loads myAPI.dll and a myserver.exe that runs
authentication/association engine etc so I am not sure if I merge them then I
would be able extend it in future.
Anyways I went to all the links mentioned by you and have few questions
1) On CE it seems that device.exe hosts both the wzcsvc.dll and wzcsapi.dll
so I want to know if I can also host my myserver.dll and myapi.dll also on
device.exe. If yes then I guess there won’t be any interprocess communication
issues. Is it correct? Also I am assuming that my UI code has to be part of
myapi.dll else I will see the same interprocess communication. Do my dll has
to be signed if it has to be hosted by device.exe?
2) If instead of device.exe I use services.exe mentioned by you then it is
mentioned that my “service DLL has to be signed to be trusted and loaded by
services.exe” so does it mean that every time I change the version of my dllI
have to get signature files from Microsoft? Also services.exe works on
client-server model but my server(myserver.dll) has to issue notifications
to the client so I guess in that scenario services.exe won’t be helpful. Is
this correct?
3) So I might end up writing an myui.exe that will host my single dll
(myserver.dll+ myapi.dll) and I want to know if it is preferred option in CE
and WM5.

Thanks
aguliani


"John Spaith [MS]" wrote:

Windows CE 5.0 (general embedded) actually does have an out-of-proc COM
Server (you'd need SYSGEN_DCOM, see
http://blogs.msdn.com/cenet/archive/2005/04/27/412600.aspx about adding
components to a CE device). You're right though on WM5 you wouldn't have
out of proc COM, so best not to mess with it.

I have a blog about different IPC mechanisms on CE -
http://blogs.msdn.com/cenet/archive/2005/07/13/438424.aspx. In this case,
if you have a clear differentiation between a client & server piece to this
(eg part A always calls part B), then you could potentially move the server
part into services.exe where you can create a special fcn to receive calls
like this, this is in fact how we on CE port RPC servers -> CE. White paper
on services at http://blogs.msdn.com/cenet/archive/2004/12/15/316007.aspx.
(My long-term goal is to be able to answer any newsgroup questions via blog
links :)).

For your case, have you considered a bigger rearchitecture and putting both
the executables into one giant executable so you can just use in-proc COM?
This would be easiest, though don't know if architecture lends itself to
that or no.

--
John Spaith
Development Lead, Windows CE
Microsoft Corporation

Check out the CE Networking Team Blog at http://blogs.msdn.com/cenet/.

This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2006 Microsoft Corporation. All rights
reserved.

"aguliani" <aguliani@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D67B002C-0452-4B25-A002-EB9044A99924@xxxxxxxxxxxxxxxx
I have an application that uses COM OutProc server and I have to port it to
WinCE 5.0 and WinMobile 5.0 and I found out that COM outproc server is not
supported on WinCE 5.0.
One option for me is to remove COM and implement my own RPC server and
client but this might take so is there any way to make existing code work
on
winCE. I am also using Monikers in my code.

aguliani



.

Relevant Pages

  • Re: Unable to print to networked printer - get access denied messa
    ... Check the permissions on the server assuming the client has a true RPC ... How is the Standard TCP/IP port configured for the device? ...
    (microsoft.public.windowsxp.print_fax)
  • Re: interfaces lo:1 lo:2 lo:3? (for remote ssh tunnels)
    ... That's the problem tunneling (port forwarding) solves. ... >>can't get past the client firewall. ... > I don't understand why the server would be making the ... server initiates another connection to the client -- in this ...
    (Debian-User)
  • Re: Remote Connection Issue
    ... through port number 3389 and a workstation on the LAN through port number ... I understand that you want to allow a LAN client ... and you have configured server publishing rule ... > By default Terminal Server and Windows 2000 Terminal Services uses TCP ...
    (microsoft.public.windows.server.sbs)
  • Re: RealVNC
    ... Default listening port for RealVNC server that runs on the machine on which ... Then there is default Java listening port on port 5800 on the client machine ...
    (microsoft.public.windows.server.sbs)
  • Re: Redirecting data sent to a local printer to another host and port on the network
    ... All client workstations have access to the ... simply redirecting netcat traffic on port 9100 to port 515 on ... Only LPR clients talk to LPD print server daemons. ... >workstation at the branch site where the print job originated. ...
    (comp.unix.sco.misc)