By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,626 Members | 1,929 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,626 IT Pros & Developers. It's quick & easy.

.Net Remoting - Did something change from '2003 to '2005?

P: n/a
I've been using Remoting in VB 2003 app's for a while now.

Over the last couple of days, I've been playing around, trying to use
Remoting to talk to a '2005 Windows Service.

If I set up the client with a configuration file ...

<configuration>
<system.runtime.remoting>
<application>
<client>
<wellknown
type="[-class-name-], [-assembly-name-]"
url="tcp://localhost:[-port-]/[-uri-]"
/>
</client>
<channels>
<channel ref="tcp" port="0"/>
</channels>
</application>
</system.runtime.remoting>
</configuration>

.... everything works as expected; Remoted objects are loaded and run.

So why am I complaining?

Under VB '2003, I /didn't/ need to have any of this; I just added - in
code ...

Dim sURI As String _
= "tcp://localhost:[-port-]/[-uri-]"
Dim oPlugin As Plugin _
= DirectCast( RemotingServices.Connect( _
GetType(Plugin) _
, sURI _
))
Dim sRequest As String = ...
Dim sResult As String _
= oPlugin.Execute(sRequest)

If I try the above code (that /used/ to work; I have it in loads of
client applications), I get a connection to the service (if I kill the
service, I get the "connection forcibly closed" exception in the client)
but the remoted objects never get loaded or executed.

Any ideas?

TIA,
Phill W.
Aug 2 '07 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.