Windows CE and remote objects

[Guest]

Hello everybody,

I've developed Remoting components running on a desktop (with .NET *regular* framework)

I have a couple of industrial PDAs running Win CE .NET 4.1 that need to connect and use these 'desktop' components over a WLAN (wifi LAN).

Obviously the compact framework does not support Remoting.

What should I do? can I use Webservices (via SOAP) or should I go back to DCOM??

* scenario 1:
WinCE <--- http+soap ---> Desktop .remoting object (without a webservice?

* scenario 2:
WinCE <--- dcom ---> Desktop DCOM object (converted from C#


Any hint is highly appreciated !

Sincerely,

Bertrand

 

[Chris Tacke, eMVP]

A Web Service should work fine, depending of course on the exact call you
need to make.

--
Chris Tacke, eMVP
Co-Founder and Advisory Board Member
www.OpenNETCF.org
---
Windows CE Product Manager
Applied Data Systems
www.applieddata.net

Hello everybody,

I've developed Remoting components running on a desktop (with .NET *regular* framework)

I have a couple of industrial PDAs running Win CE .NET 4.1 that need to

connect and use these 'desktop' components over a WLAN (wifi LAN).

 

[Daryl Davis]

As a step in this thread, I have a question,

I currently have 70 + desktops using mts to access a sql server. The dlls
on are all writen in vb6.

I would like to put some wireless units on this network running ce.

Best case senario for me would be for the ce.net application to access these
dlls as they already contain the important info and have already be written.

Is there someway I can make this work? Is there an example out there that I
can look at?
Thank you,
Daryl R Davis

 

[Chris Tacke, eMVP]

Write a web service that exposes functions callable by the CF and that in
turn instantiate the COM or DCOM objects in your DLL. This way the WS acts
as a "proxy" for the calls, marshaling data in and out.

 

[Paul G. Tobey [eMVP]]

You can't reuse the DLLs, no. They're written, for one thing, for the x86
processor which is not found in any Pocket PC devices. Further, the DLL
headers indicate a different OS and they wouldn't work on CE anyway.

You might be able to convert the DLLs to managed code in VB.NET and then
generate them for .NET CF, allowing you to use them both on the desktop and
Windows CE, but it's likely that a different interface is going to be
exported, if you try to do that, so existing applications will also have to
be rewritten.

On the other hand, you may be able to port your VB6 code to C++ and compile
it natively for Windows CE using eMbedded Visual C++. Requires some
significant work, but at least the changes are localized to the DLLs, not
spread around to the applications, too.

Paul T.

 

[Daryl Davis]

So I need to learn to create the Web Service. I remember seeing it in the
101 examples.
Thank you.
Daryl

 

[Daryl Davis]

This looks like extensive work. I will look at doing this for new code.
Thank you.
Daryl Davis

 

[Gordon Freeman]

CEfusion lets you make COM calls from CE to MTS.
http://www.odysseysoftware.com/cefusion_main.html