No System.Runtime.Remoting in CompaceFramework?

[Andreas Mahub]

Hello from Germany,

i have a little question. I have wrote a program in VB.NET. A second program
can connect to the masterprogram from a notebook or other pc's in my
network. This use the namespace System.Runtime.Remoting.

I would like wrote a program for my pocketpc (Acer n311 with Windows CE
5.0). But in the CompactFramework i can not find the System.Runtime.Remoting
Namespace.

Is this namespace not in CompactFramework or can i find/use a other?
I hope you can help me.

Best regards
Andy

 

[Andreas Mahub]

Hi again,

i have found my failure. I have the System.Runtime.Remoting in my project.
But i can not found the system.uribuilder. Is the last error. Here is the
function:
Private Function ConnectToServer() As ServerFunctions
Try
Dim ServerURL As String
Dim URL As New UriBuilder
With URL
.Scheme = "tcp"
.Host = "192.168.48.21"
.Port = _Port
.Path = _MyAppName & "/" & MyURI
End With
ServerURL = URL.ToString

' Serverobjekt ermitteln
ConnectToServer =
CType(Activator.GetObject(GetType(ServerFunctions), ServerURL),
ServerFunctions)

Catch ex As Exception
_ConnectError = True
End Try
End Function

The UriBuilder and Activator can not found in Namespace System.
What can i do?

Regards
Andy

 

[Guest]

Remoting is not supported in the CF.


--

Chris Tacke, Embedded MVP
OpenNETCF Consulting
Giving back to the embedded community
http://community.OpenNETCF.com

 

[Andreas Mahub]

Hi,

I have see it in the last hours :-(
Gives a other way for communicate with my mainprogram?

Best Regards
Andy

 

[siccolo]

Hi,

I have see it in the last hours :-(
Gives a other way for communicate with my mainprogram?

Best Regards
Andy

"<ctacke/>" <ctacke[at]opennetcf[dot]com> schrieb im Newsbeitrag

Remoting is not supported in the CF.

Chris Tacke, Embedded MVP
OpenNETCF Consulting
Giving back to the embedded community
http://community.OpenNETCF.com

depends on what you mean by "...communicate with my mainprogram..." -
may be using web service(s) will help?


... more at http://www.siccolo.com/articles.asp ...

 

[Bjørn Brox]

Hi,

I have see it in the last hours :-(
Gives a other way for communicate with my mainprogram?

Best Regards
Andy

"<ctacke/>" <ctacke[at]opennetcf[dot]com> schrieb im Newsbeitrag

Remoting is not supported in the CF.
--
Chris Tacke, Embedded MVP
OpenNETCF Consulting
Giving back to the embedded community
http://community.OpenNETCF.com
Hello from Germany,
i have a little question. I have wrote a program in VB.NET. A second
program can connect to the masterprogram from a notebook or other pc's in
my network. This use the namespace System.Runtime.Remoting.
I would like wrote a program for my pocketpc (Acer n311 with Windows CE
5.0). But in the CompactFramework i can not find the
System.Runtime.Remoting Namespace.

depends on what you mean by "...communicate with my mainprogram..." -
may be using web service(s) will help?

I would definitely recommend using a web-service to communicate with
your server/home office because all other communication methods require
that you first open a connection to Internet manually.

 

[Paul G. Tobey [eMVP]]

Just ordinary sockets works fine, too, if you don't have a Web server on the
machine to which you want to communicate.

Paul T.

Hi,

I have see it in the last hours :-(
Gives a other way for communicate with my mainprogram?

Best Regards
Andy

"<ctacke/>" <ctacke[at]opennetcf[dot]com> schrieb im
Newsbeitrag


Remoting is not supported in the CF.
--
Chris Tacke, Embedded MVP
OpenNETCF Consulting
Giving back to the embedded community
http://community.OpenNETCF.com
Hello from Germany,
i have a little question. I have wrote a program in VB.NET. A second
program can connect to the masterprogram from a notebook or other pc's
in
my network. This use the namespace System.Runtime.Remoting.
I would like wrote a program for my pocketpc (Acer n311 with Windows
CE
5.0). But in the CompactFramework i can not find the
System.Runtime.Remoting Namespace.

depends on what you mean by "...communicate with my mainprogram..." -
may be using web service(s) will help?

I would definitely recommend using a web-service to communicate with
your server/home office because all other communication methods require
that you first open a connection to Internet manually.

 

[Bjørn Brox]

Paul G. Tobey [eMVP] skrev:

Just ordinary sockets works fine, too, if you don't have a Web server on the
machine to which you want to communicate.

Last time I tested ordinary sockets on Windows Mobile 5 or 6 the unit
did NOT connect to Internet automatically, i.e. started a dial-up GPRS
or 3G connection or whatever communication method that was available.

I know that you can use some connectionmanager with OpenNetCF or
similar, but then you are not using an ordinary socket connection.

By using a http connection to speak with a webservice you go around all
these problems.

The web-service was easy to set up using the built-in IIS on XP Pro.

 

[Paul G. Tobey [eMVP]]

Yes, that's true, with phone-based networking. You can tell it to connect,
when you need it, just as the browser does. You can easily arrange your
code so that this is transparent and even so it doesn't occur if a WiFi
network is available, or if you're plugged into a PC with ActiveSync.

I'm confident that my network administrator would not open port 80 on our
firewall to allow me to connect to a random PC with Web Services, any more
than doing so for a random socket connection. For on-premise applications,
which is a pretty high percentage of the things which you'd use remoting
for, it's not a problem, though.

Paul T.

Paul G. Tobey [eMVP] skrev:

Just ordinary sockets works fine, too, if you don't have a Web server on
the machine to which you want to communicate.

Last time I tested ordinary sockets on Windows Mobile 5 or 6 the unit
did NOT connect to Internet automatically, i.e. started a dial-up GPRS
or 3G connection or whatever communication method that was available.

I know that you can use some connectionmanager with OpenNetCF or
similar, but then you are not using an ordinary socket connection.

By using a http connection to speak with a webservice you go around all
these problems.

The web-service was easy to set up using the built-in IIS on XP Pro.

 

[Guest]

A Just to be clearn, if you use COnnectionManager first, that doesn't affect
the socket. You are indeed still using a socket. A web service call
doesn't do any magic to auto-enable the connection - it uses the connection
manager to ensure a connection is open before making the call. The same
thing can be done for basic sockets, FTP, telnet, WCF or whatever mechanism
of communication you want, it just isn't always done for you.


--

Chris Tacke, eMVP
Join the Embedded Developer Community
http://community.opennetcf.com

Paul G. Tobey [eMVP] skrev:

Just ordinary sockets works fine, too, if you don't have a Web server on
the machine to which you want to communicate.

Last time I tested ordinary sockets on Windows Mobile 5 or 6 the unit
did NOT connect to Internet automatically, i.e. started a dial-up GPRS
or 3G connection or whatever communication method that was available.

I know that you can use some connectionmanager with OpenNetCF or
similar, but then you are not using an ordinary socket connection.

By using a http connection to speak with a webservice you go around all
these problems.

The web-service was easy to set up using the built-in IIS on XP Pro.

 

[Bjørn Brox]

Paul G. Tobey [eMVP] skrev:

Yes, that's true, with phone-based networking. You can tell it to connect,
when you need it, just as the browser does. You can easily arrange your
code so that this is transparent and even so it doesn't occur if a WiFi
network is available, or if you're plugged into a PC with ActiveSync.

Can you dig up some examples on how to manage this (without OpenNetCf)?

....

 

[Guest]

The OpenNETCF libraries aren't using any secret stuff. The best example of
how we did it is, to be honest, to pay the $50 fee and look at the code that
comes with the SDF Extensions for Studio. If the price you'd typically pay
for a tech book is too steep for you then you can always look at the
Connection Manager API documentation on MSDN - it's pretty straightforward -
and the simply write a P/Invoke wrapper for it (and what you end up with
will be pretty much the same thing we've done).

I don't recall seeing any thorough specific managed code examples of calling
into the connection manager.

--

Chris Tacke, eMVP
Join the Embedded Developer Community
http://community.opennetcf.com

Paul G. Tobey [eMVP] skrev:

Yes, that's true, with phone-based networking. You can tell it to
connect, when you need it, just as the browser does. You can easily
arrange your code so that this is transparent and even so it doesn't
occur if a WiFi network is available, or if you're plugged into a PC with
ActiveSync.

Can you dig up some examples on how to manage this (without OpenNetCf)?

...

 

[Paul G. Tobey [eMVP]]

I don't follow. You need to control the Connection Manager. The help from
the native SDK for your target device should give you the necessary
information on what calls are available and what parameters are appropriate.
I don't have any reason to want to rewrite the same code that's already in
OpenNETCF. If it were I, I'd just either get the community edition or buy
the full edition and use what I needed. If, for some reason, you can't use
OpenNETCF (I still haven't heard a reasonable one), certainly the boss will
understand that avoiding it has costs.

http://msdn2.microsoft.com/en-us/library/aa455880.aspx

http://msdn2.microsoft.com/en-us/library/aa455877.aspx

Paul T.

Paul G. Tobey [eMVP] skrev:

Yes, that's true, with phone-based networking. You can tell it to
connect, when you need it, just as the browser does. You can easily
arrange your code so that this is transparent and even so it doesn't
occur if a WiFi network is available, or if you're plugged into a PC with
ActiveSync.

Can you dig up some examples on how to manage this (without OpenNetCf)?

...