I'm using remoting CAO's and singletons and getting a
on the server Whenever a client is closed down.
I'm fairly new to remoting and .net in general and was wondering if I am
closing the client app in the correct manner. All examples I've seen do
not specify methods of closing down the client and seem to just allow
the remote objects to expire, is this correct?
I am also usig McAfee Firewall and antivirus but the problem persists
even if they are diasbeled.
Also the the OverlappedAsyncResult part is cofusing as I am not using
asyncronous method calls.
I'm pretty sure this is a problem with my code and not an unresolvable
issue as described above any sugesstions on where how to resolve this
would be appreciated or even a shove on the right direction would be
The client and server are both running on localhost, the remoting server
does make use of a web service to retrieve some data but I'm 80% this is
unrelated as the all works fine while the remoting client is running.
I'm using Windows XP professional and the Server offers two SAO
singlecall, one singleton and one CAO is there an proper method of
disconnecting from remoting objects?
Also the problem only occurs about 80% of the time.
*** Sent via Developersdex http://www.yqcomputer.com/
Don't just participate in USENET...get rewarded for it!